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

Clicking anywhere generates JS warnings in Firefox iff a dropdown menu is present #7318

Closed
qdelettre opened this issue Mar 18, 2013 · 17 comments
Labels

Comments

@qdelettre
Copy link

I create another issue about this problem, as it is still not solved.
See #5566

The JS warning is
Empty string passed to getElementById().
elem = document.getElementById( match[2] );

I use FF 19.0.2 with twitter bootstrap 2.3.0 or 2.3.1 and still clicking anywhere makes a warning in firebug.

Have i missed something ?

@cvrebert
Copy link
Collaborator

Could you make an updated jsFiddle to demonstrate?

@qdelettre
Copy link
Author

As in #5566 with latests jquery and bootstrap, http://jsfiddle.net/pZT5W/5/ reproduce the error.

@NetserveMalta
Copy link

I have exactly the same problem... BS 2.3.1 and jQuery 1.9.1

@Merg1255
Copy link

issue is valid.

@cvrebert cvrebert mentioned this issue Mar 22, 2013
@colapiombo
Copy link

i have the same problem problem

BS v2.2.2 and jQuery 1.8.3

@edragame
Copy link

edragame commented Apr 4, 2013

Same issue.
BS 2.3.0 JQuery 1.9.1

@c0achmcguirk
Copy link

Issue is legit. Firefox 20.0, FireBug 1.11.2, JQuery 1.9.1, BS 2.3.1

@ghost
Copy link

ghost commented Apr 8, 2013

Same issue.

@justindarc
Copy link

I am also experiencing the same issue. Firefox 19.0.2 on Mac OS X 10.8.3, jQuery 1.9.1

@shishirmk
Copy link

I am facing the same problem on FF 20, jQuery 1.8.3 , Boostrap 2.3.0

@cvrebert
Copy link
Collaborator

Thanks, I think we have quite sufficient confirmation now.

@BenjaminRH
Copy link

Experiencing this problem. FF 20 on Ubuntu 13.04, jQuery 1.8.3, Bootstrap 2.3.1.

@shishirmk
Copy link

Just sent a pull request to fix this bug. #7692

@MrUpsidown
Copy link

Great. Hope this will get a fix soon by BS team.

@mdo
Copy link
Member

mdo commented May 17, 2013

Just pushed a 2.3.2 patch that I believe addresses this.

@jason-slack
Copy link

I am still experiencing this problem even using bootstrap 2.3.2

screen shot 2013-05-23 at 10 50 35

@cvrebert
Copy link
Collaborator

@jason-slack: See #7692. It'll be fixed in v3; they aren't going to do anything about it in v2.

@albertmatyi
Copy link

A possible solution is not to use <a>nchors with href="#" property which is still valid. Then these warnings will stop to appear.

Explanation

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

No branches or pull requests