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

Problems when navigating back or forward in Chrome #29

Open
Moorst opened this issue Feb 24, 2015 · 6 comments
Open

Problems when navigating back or forward in Chrome #29

Moorst opened this issue Feb 24, 2015 · 6 comments

Comments

@Moorst
Copy link

Moorst commented Feb 24, 2015

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.

image

If you click this select, you'll notice the error "Uncaught TypeError: Cannot read property 'getBoundingClientRect' of undefined" in the console

image

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".

image

@purpleweb
Copy link

I have exactly the same issue.
Is there a solution ?
Thx

@Moorst
Copy link
Author

Moorst commented Mar 17, 2015

I haven't been able to find one :(

@lukechapman
Copy link

@tonioMtl @Moorst -- did you guys ever find a solution to this?

@vestman
Copy link
Owner

vestman commented Dec 22, 2015

@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.

@lukechapman
Copy link

@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 value attribute being set on the first option element) but I'll definitely wait till your fix!

@sfacs
Copy link

sfacs commented Aug 9, 2017

I'm having the same issue, and the first option element has a value set. The link @vestman posted seem dead, and it seems this never got pushed to master. If you happen to still have the fix I would greatly appreciate it!
Thanks!

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

5 participants