Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

INVALID_STATE_ERR with Chrome 16 #66

Closed
jab opened this issue Oct 11, 2011 · 2 comments
Closed

INVALID_STATE_ERR with Chrome 16 #66

jab opened this issue Oct 11, 2011 · 2 comments

Comments

@jab
Copy link
Contributor

jab commented Oct 11, 2011

Using the latest webshims with the latest Google Chrome Canary build (16.0.904.0), I'm getting:

Uncaught Error: INVALID_STATE_ERR: DOM Exception 11

(and also "polyfiller.js:15Polyfilling takes a little bit long").

I'm using webshims like so:

$.webshims.activeLang('en');
$.webshims.setOptions('forms', {replaceValidationUI: true});
$.webshims.polyfill('forms');

Apologies if this is a bug in Chrome and not webshims.

@aFarkas
Copy link
Owner

aFarkas commented Oct 11, 2011

Hi,

thanks for your bugreport. It is indeed a chrome bug. My newest commit deals with this. But I hope, that this will be fixed before Chrome 16 goes stable. I will observe this in the beta channel and if it's still there, I will file a bug.

About the message "Polyfilling takes a little bit long". This message comes, if polyfilling takes more than 600ms. I have changed this message from "warn" to "info", so that it should be only visible, if you do set $.webshims.debug = true;.

If this message comes only if this error occurs, than everything should be fine. If it's comming in Chrome 14 or FF7 and you are only loading the "forms" feature, you really should look into the networkpanel to detect why it takes so much time.

You can also give me the URL to look into this.

cheers
Alex

@jab
Copy link
Contributor Author

jab commented Oct 11, 2011

confirmed, 30b1002 fixed the error and the warning. thanks for the super quick turnaround and great explanation as usual!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants