-
Notifications
You must be signed in to change notification settings - Fork 132
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
Problems when navigating back or forward in Chrome #29
Comments
I have exactly the same issue. |
I haven't been able to find one :( |
@tonioMtl @Moorst -- did you guys ever find a solution to this? |
@lukechapman , @tonioMtl, @Moorst, I'll push a fix in a day or two. I've rewritten the way the placeholder is shown and that seems to have fixed the issue. Here's a test I uploaded a day or two ago: http://vst.mn/selectordie_tmp/?test In the minified JS above there's a couple of other changes and some tmp code, so if you can wait I'll push the fix in a day or two. |
@vestman Thanks a bunch! I just actually came back to say I found a way to fix it (for me it seemed to be a result of no |
I'm having the same issue, and the first |
For some reason, when you navigate back or forward in chrome, some of the select fields break. This is even happening on your demo site.
To reproduce:
You'll notice then that the first select on your demo page is empty.
If you click this select, you'll notice the error "Uncaught TypeError: Cannot read property 'getBoundingClientRect' of undefined" in the console
The rest of the selects work, other than the one in the "Disable / Enable" section. If you click on this select, you get another error "Uncaught TypeError: Cannot set property 'nodeValue' of null".
The text was updated successfully, but these errors were encountered: