#147 closed bug (fixed)
Including jQuery again overwrites already registered document-ready events
Reported by: | Jörn | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | event | Version: | |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
By including jQuery again, all document-ready events are lost. If you can see the text below, the problem still exists. This problem exists in enviroments, where the page author controls only a part of the document, like Portlets (Java JSR 168). While it is possible workaround this by only including jQuery when it is not loaded yet, it would be much more convienent to have that built into jQuery itself.
Example: http://fuzz.bassistance.de/overwriteBug/overwriteBug.html
Change History (3)
comment:1 Changed 16 years ago by
Priority: | minor → major |
---|
comment:2 Changed 16 years ago by
comment:3 Changed 16 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fixed in SVN, tested in FF 1.5.0.6, IE 5.5 SP2 and IE 6, Opera 9.01, Safari 1.3.x.
Note: See
TracTickets for help on using
tickets.
It might by suffice to include a check for an existing jQuery variable at the start of the script. Something like:
I'm no fan of wrapping the code into one monster if. Is there some kind of return oder quit/exit inside a single javascript file?