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.
Related
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.
I'm working on a small website and I'm writing a website almost from scratch. I'm using Bootstrap 4 and I'm modifying only basic CSS.
Whenever I open the Chrome Devtools, the website completely flips out and it looks like it keeps reloading. The entire website only loads from localhost, however, the network tab keeps showing repeating requests to the saem assets, over and over again. The second I quit Devtools, the entire behavior stops. I've tried installing a cache killer, tried incognito, but the problems keeps appearing.
I'm also using Octicons, and what I have noticed is that when I manage to get the Devtools to at least stay focussed at the right part, the <i class="oi oi-chevron-right"> node keeps flashing in purple, indicating there is a change to that node. I can't open it and even just clicking on it won't help, the entire CSS keeps shifting in the inspector bar and it seems like something is making rapid changes. It appears that Chrome re-applies styling changes that I made a few days back, such as locally modifying the margin of an element.
I was able to work on the website just fine a few days ago, but even moving back in commits won't keep the problem from happening. I am starting to think it is a bug with Chrome, but I can not confirm this in any way.
Is there anything that is known to break Chrome's Devtools, that might explain this behavior, or is there a way to clear the cache of the Chrome Devtools specifically?
The "Changes" tab in Devtools reports that there are no changes, but the CSS I see on page makes me seriously doubt it. Removing the icons entirely does not seem to resolve the problem, so I think the issue lies elsewhere. Breakpoints are not triggered either.
I'm not sure but,
Have you checked the chromium extension program?
i have a website with alot of popup windows and z-index going on.
Chrome version: 46.0.2490.80 m (never seen in other browser, but cannot omit it)
Everything works fine, but every 50th (not precisely, but very rarely when opening popup or coming back from alt-tab)
Behind all this: my website.
The red: the fullscreen overlay beneath my popup.
The lightGray: my popup window.
The darkgray: popup content.
So for some reason, the corner of my div is cut off. The problem is not connected to this particular popup, or this particular corner.
I have sometimes seen this following an alt-tab into chrome, but not enough to say that's the problem.
I have never seen anything like this, usually it works or breaks, this time its working breaked.
Any clues?
after visiting a website for a long time, and leaving another open during that time, it seems that the layout of the first, appears on the second. It happens mainly when using chrome, but once the issue appears on chrome, it is as if it stays in memory, and happens in firefox too. I read about memory leaks, but I am not sure that this is the issue, and if I am the only one that has it. I mainly see it happening on the website that I am working on which is why it is an issue, but it happens on the black bars of facebook, and another website called jeuxvideo.com . (This is the template my website uses: http://themes.alessioatzeni.com/html/brushed/).
Here is an image showing the issue, where the layout of youtube overlays another website (the transparent grid you can see over the rest of the website):
http://i.imgur.com/FQW7Jin.jpg
Is this a bug with chrome? Because I have looked everywhere and it doesn't seem that anyone else has this issue, or maybe it is just my computer?
This is probably image persistence, where the colours in the monitor get "stuck" temporarily after being on or off for a long time. The fix would be to upgrade the monitor.
You could confirm this by taking a screenshot while the problem is happening. If you don't see it in the screen shot (try moving the screenshot around the monitor when you see the problem, do the affected areas of the screen move too? or are the artefacts stuck in place?) then the problem is with the hardware.
I am running into a random issue in a website that I am working. This website contains many images and some images are 1Mb in size or bigger. The site also uses some CSS3 tricks, like 3D rotations.
Since I added this 3D CSS stuff, I noticed a problem in Google Chrome where some random areas in the website are not rendered.
This is a screen-shoot of how the site should be rendered, the green lines are because I've enabled the "Composited render layer borders" on chrome://flags:
And this is how it get rendered when the issue happens:
This white squares appear randomly and they can disappear or reappear in another place if the scroll the website. I also noticed that this problem is more common in lower-end computers so I my guess is that somehow Chrome is running out of GPU memory.
Why this problem happens? and is the any workaround for it (besides disabling the 3d CSS)?
In case it helps, this is the website:
http://colocation.cubo.cc/cheetos/masterbrand/
Update:
I raised a issue for the Chrome team.
I couldn't reproduce this problem in the Chrome Canary.
It was a Chrome Issue, and its fixed now:
http://code.google.com/p/chromium/issues/detail?id=121779
I can only congratulate the Chrome team for pushing bugfixes so fast, I wish IE was like this.