We run the graphical part of our software in Canvas. With the latest version of Google Chrome (v77) being released, our product doesn't display anything on load. Canvas simply doesn't draw anything.
When you resize the windows or scroll, Canvas draws the elements correctly, but not initially. For every refresh, we are back to a blank page.
If we disable Accelerated 2D canvas, it works. We have tried the upcoming versions of Google Chrome (v78 and v79), and here canvas renders and draws correctly.
Does anybody experience anything similar, i.e. is it a Chrome bug?
Dropzonejs doesn't work with Chrome 77 on Android. It is probably same isue with canvas.
more on this isue here
Related
Noticed that when I go to view a 3d model on my iPhone (using the latest version safari or chrome), the full-screen button doesn't work. Anyone seeing this problem and has figured out a solution?
Public example you can try on your phone.... https://autodesk-forge.github.io/viewer-javascript-offline.sample/
This is a known issue and is being addressed by the Dev team. Stay tuned to the official Forge blog for release notes of future versions of Viewer to keep tabs on the fix.
In the meantime one can work around by programmatically toggling the toolbar (there's no display cube on mobile either):
viewer.toolbar.setDisplay('none') //hide
viewer.toolbar.setDisplay('block') //show
You can come up with a button of your own as the control for this.
I have many markers in clusters, one of them with 3 markers in it.
But when I open it, I see only one marker.
If I open developer console in browser or change zoom I see all of them.
What I need to do to prevent it
P.S: I catch this error only in Safari. In Firefox and Chrome everything work fine
This appears to be a CSS problem. No JavaScript code path differences are apparent between Firefox (which works) and Safari (which does not).
In the Cluster.prototype.addMarker() function, removing the "this.markers_[i].setMap(null);" lines, which caused the clusters to remain on the map, though they are cut off as though by a bounding box (see attached screenshot; note that both clusters are cut off at the bottom, at different positions). This leads to believe that the action of hiding the existing markers when creating the cluster icon is causing the cluster itself to be hidden by a misplaced bounding box. This might be the reason for your markers being not displayed at a certain zoom level or zoom action.
This is a problem(bug) with Safari 5.1, you can try with an older version 5.0.5 or the newer version 5.1.1, it should work as expected.
I'm having an issue with flot graph and Google Chrome.
The problem is reproduceable as follows:
Open an flot graph
Lock your screen
Unlock your screen and you will have to refresh the page to repaint the graph
It works fine under Firefox and IE.
Does anybody know how to resolve this issue?
It's probably a Chrome hardware-accelerated canvas bug. Try visiting chrome://flags and turn off hardware-accelerated canvas, then see if the problem persists. If it goes away, then you know that it was due to some interaction between Chrome, your graphics driver, and your graphics card, and you should file a bug with the Chrome team.
Thanks for your reply
My setting were
Disable accelerated 2D canvas
Enable
I assume hardware acceleration is now off, and it is not working
Clicking on enable and it is working.
The problem has to with the hardware acceleration, I can se that now.
But I have to turn it ON and not OFF to get it working
Thanks again
I have a Windows 7 tablet (an ASUS EP121), and I am using a web browser to display a Google Maps-based web application that I have created. Basically, I want the pinch gesture to zoom the Google Map (similar to using the scroll wheel to zoom a Google Map when using a mouse), rather than zooming the entire web page.
In Opera, Firefox, and Chrome, the pinch gesture simply zooms in the entire page. This behavior makes perfect sense for most use cases, but I'm wondering if there is any setting, in any of these browsers (e.g., Opera, FF, Chrome) that can cause the pinch gesture to behave like a mousewheel instead of zooming in the entire page?
Interestingly enough, in Arora, the pinch gesture can be used to zoom in/out a Google Map; however, other issues are preventing me from using Arora effectively that I think will be more difficult to address than the issues I am raising in this question.
Another option would be to disable pinch gestures (I know this is possible in Firefox, I'm sure the other browsers have some means to do the same), and then try to let the application take care of it. Are there any thoughts on going this route? Would something like jQuery mobile be able to accomplish this?
As a last resort, I could use Qt's webkit and implement my own event handling (basically creating a stripped down Arora), but I'm really hoping there's an easier way that utilizes currently available browsers.
Thanks.
If anyone ever runs into the same problem that I had here, I have created a very simple WebKit-based web browser using Qt that implements a pinch gesture and uses it to fire off a scroll wheel event.
It works quite well (especially for Google Maps) and the source is available on github here. I've tested the code on Windows 7 and Ubuntu Linux 12.04; it works without any problems.
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.