I've encountered a strange bug which I'm not able to solve for some time.
The bug appears in Firefox when scrolling in certain resolution (Macbook pro 2019 15", 1680x1050) - product elements (not only images) start to flicker.
I've made a video of the bug: https://www.youtube.com/watch?v=xByt25fbaYs
Now this is where it gets weeeird:
If i open dev tools - the flickering stops. If dev tools are closed, the flickering stops. Until pages is reloaded
If I change resolution settings or just resize the browser, flickering also stops.
Link to the problem: http://vilmers.vsbl-dev.lt/sofas/
Any help or suggestions would be appreciated a lot.
Thanks!
Ok, so I don't know why but while debugging I've set elements which were disappearing background colour and it fixed the issue for some reason.
Related
I have a site (http://www.iproconnect.com.au/) that for one user (that I know of) renders the home page with black areas in Firefox. These do not seem to be tied to CSS, as if I force a re-draw of an affected area (e.g. by scrolling areas in and out of the viewport) it sometimes renders correctly, and sometimes incorrectly but differently to the previous incorrectly. Also if I do this with the inspector open, no CSS seems to change, and hovering background URLs show the image downloaded correctly.
I can't reproduce this in other installations of Firefox (all running the same version - fully up to date). And this user has un-installed and re-installed with no change in behavior.
I don't even know how to debug this further, let alone how to solve. Any ideas greatly appreciated.
On my site, infinitech.org/beta, on mobile devices, pulling out the menu has EXTREME lag. Closing this menu also causes severe lag. I'm using a core-scaffold. Can anyone think of what's causing this? I'm using Polymer 0.5.4. Thanks!
Have you solved this problem? Have the same issue. Drawer opens very slowly while main screen blinking grey and black. In browser it's ok but on Nexus5 it always reproduces.
UPD. I have found problem.
You should go to bower_components/core-drawer-panel/core-drawer-panel.css
And delete "opacity: 0;" for element #scrim. Works perfectly!
When I bring up the dev tools in Chrome Canary, it just appears as a black box. I have it set to display in another window rather than overlaying the actual page, but as said, the inside of this window is just black. If I hover the mouse over it, it highlights the elements on the page accordingly.
I have tried: Looking for settings to dock it back into the screen, restarting CC, restarting my computer, reverting to default settings in the CC menu. None of this has changed a thing unfortunately.
EDIT: Has been resolved with update to version 33.0.1707.0
Same thing happened to me, starting sometime in the past two days. I tried everything you did and also tried reinstalling Chrome Canary, no dice. My solution was to dock the developer tools back to the main browser window by clicking in the upper-right corner of the black box, where I think the dock icon usually is.
In the recent versions of Chrome we have started to get a very annoying problem with our GWT-application.
On some page loads we get a big white overlay almost covering the whole application.
Anyone seen this and know what is causing it?
I've tried to inspect with developer tools but the frame doesn't seem be any html-element.
A resize or reload of the window/page resolves the problem.
Having a slight problem with
http://jquery.com/demo/thickbox/
In IE8, the overlay window doesn't scroll when you scroll down in the browser. So if you click something at the bottom of the browser window, the overlay window pops up but at the top of the screen so you have to scroll back up. This only happens in IE8, all other browsers the overlay window follows. Help? Thanks
I had the same problem, but only when using <frames> or <iframes>. Being unable to correct the problem, along with a few other bugs, I decided switch to using Shadowbox http://www.shadowbox-js.com/. I found it to be ALOT more flexible. Just a suggestion. But as for the IE8 problem you reported, I never encountered the issue in a parent window, just when using frames.