#3459 closed defect (invalid)
Compataiblity problem with MooTools on load
Reported by: | guest | Owned by: | James Burke |
---|---|---|---|
Priority: | high | Milestone: | 1.0 |
Component: | Core | Version: | 0.9 |
Keywords: | MooTools onLoad addOnLoad | Cc: | [email protected]… |
Blocked By: | Blocking: |
Description
We have noticed that there seems to be a problem when mootools is loaded in the same page as Dojo. MooTools? has its own onLoad dispatcher which some-how interferes with Dojo's. When further reviewed the implementaiton of the MooTools? on load behavior seems to be more compatabile with other browsers and an "expected" user behavior/interaction than that of Dojo (http://dev.mootools.net/browser/branches/1.11/Window/Window.DomReady.js?rev=606).
Requests:
Change History (7)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
Owner: | changed from anonymous to James Burke |
---|
OK, we need a testcase or a URL to demonstrate this problem before we look at it. Please provide one.
comment:3 Changed 14 years ago by
igorb: can you provide a test case within the next 2-3 days? Otherwise, I'll have to move this to Dojo 1.0.
comment:4 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:5 Changed 14 years ago by
Milestone: | 0.9 → 1.0 |
---|---|
Resolution: | fixed |
Status: | closed → reopened |
Ticket was accidentally closed, but since there is no test case, moving this for consideration in 1.0. Although, I'm tempted just to close it.
comment:6 Changed 14 years ago by
comment:7 Changed 13 years ago by
Resolution: | → invalid |
---|---|
Status: | reopened → closed |
No test case. Closing this out. Feel free to open with a test case.
I'm curious to know how the MooTools? onReady seems to be "more compatible with other browsers and an 'expected' user behavior/interaction than that of Dojo". At first glance, the Dojo and mootools things seem to take similar approaches. There may be an incompatibility problem (at first glance I don't see it), but I don't quite understand the second request. Maybe attaching a test file that indicates the incompatibility as well as maybe a test case that shows how the Dojo's addOnLoad should behave differently would help.