Chrome 9 to Chrome 10 Problems

I’m just curious if anyone else is having problems after updating from Chrome 9 to Chrome 10. I’m running Chrome 10 with Windows 7 and NVIDIA Quadro NVS 160M Driver version 260.99.

I know they disabled some stuff for Win XP but I’m having a different issue. I can still run WebGL applications in Chrome 10 but using HTML inputs is now weird. I can click on them and edit, but visually nothing happens. Ex: I can click the check box here and the lighting changes but the check box itself doesn’t

Anyone have any ideas?

Not really.

I’m on the dev track for Chrome on one machine and on the “Canary” track (nightly builds) on another. I haven’t personally seen any new issues between 9 and 11.0.670.0 (which is last night’s nightly build).

However, I do find Chrome to be generally ‘flakey’ when pushed to do difficult web pages. But it doesn’t seem to have gotten any worse.

– Steve

I’ve been using Chrome Canary (11.0.699.0) and WebGL has stopped working. I remember reading that there was some INI setting or something, but I never had to set it before. I haven’t been using WebGL as of late, so I haven’t bothered to investigate.


also with or without

Personally Ive firewalled chrome, since the automatic updates would often break webgl. On the good side it shows theyre actively working on webgl

I just downloaded 12.0.700.0 canary build of chrome and it all works fine now. I don’t know what they’re up to with the chrome builds, but as long as I have it working I’m happy. Thanks everyone.

We also got a input event problem in Chrome on Max OS. But when we force the focus to the target page, it’s fine now.

Did you find a solution?

I’m having the same problem when my Windows users had their Chrome automatically update from 9 to 10.

You can see the problem here: http://visual.local/seasons/earth/chrome10-test.html

On Windows you can click on the “Predict Average Temperature” input element but you will NOT see any blinking cursor. If you click in the input field and enter say “12” and scroll the window down and back up the entered text “12” will be visible and the text entry field will have a yellow highlight. You can click in the field again and press delete twice. Again you will see no change … but scroll down and up and the entered number will be gone.

Taking a closer look this problem only appears when I load and run the final javascript: … 10-test.js

If I don’t load this file the text input field works fine.

This works fine in Chrome 9 and also in the Canary release but not in Chrome 10.

There is a strange possible clue when I inspect the style of the input element.

On Windows there is an extra style which is the third from the top. Here’s what I see on Windows:

  1. {}

Matched CSS Rules
2) from style.css:1
{ margin: 0px; padding: 0px; }

  1. from user: agent stylesheet
    input:not([type]), input[type=“text”], input[type=“password”] { padding: 1px 0px; }

  2. from user: agent stylesheet
    input, input[type=“password”], input[type=“search”], isIndex { … }

That third element appears on Windows where I have the problem and does not appear on Chrome 10 on the Mac where I do not have the problem.

I also do not have the problem on FFv4 on Windows.

See this bug:

“experimental-webgl” breaks page on chrome 10 … l?id=71624

My only solution so far was to use the Canary build. I added a post and voted to the issue report, so hopefully they do something.