Comment #2 on issue 85615 by vange...@google.com: google.com doodle is not
clickable when accelerated 2d canvas is on
http://code.google.com/p/chromium/issues/detail?id=85615
I can repro it on windows as well both with M13 and the current canary.
It seems to have something to do with how the page detects the click on the
canvas. When the canvas element is composited, it doesn't respond to the
click. I can get the same effect in safari too if I put a translateZ(0) on
the canvas.
Comment #3 on issue 85615 by jam...@chromium.org: google.com doodle is not
clickable when accelerated 2d canvas is on
http://code.google.com/p/chromium/issues/detail?id=85615
If you can repro on m13 and this is breaking google.com, shouldn't this be
an mstone13 bug? We normally try not to break google.com in beta pushes.
The Alexander Calder doodle (Jul 21) causes rendering to stop entirely
until both canvas elements are removed from the DOM (typing a letter with
instant search turned on, or removing them manually from inspector.)
The only flag I have on is the FPS counter. It shows some rendering happens
at 2FPS, then freezes. This happens consistently on every page load.
Chrome 14.0.825.0 dev on Ubuntu 11.04
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
OpenGL renderer string: GeForce GTX 260/PCI/SSE2
OpenGL version string: 3.3.0 NVIDIA 275.09.07