Opened 15 years ago

Closed 14 years ago

Last modified 12 years ago

#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:


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 (


  • Fix the compatability problem with MooTools?
  • Re-implement Dojo's addOnLoad in the same way or a similar way that MooTools? does this

Change History (7)

comment:1 Changed 15 years ago by James Burke

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.

comment:2 Changed 15 years ago by bill

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 James Burke

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 Becky Gibson

Resolution: fixed
Status: newclosed

(In [10053]) fixes #3459 added WAI-ARIA invalid property in validate method.

comment:5 Changed 14 years ago by James Burke

Milestone: 0.91.0
Resolution: fixed
Status: closedreopened

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 Becky Gibson

yes, sorry, I transposed a bug number when I committed changset [10053] - a fix for #3549. This should remain open as the close was incorrect.

comment:7 Changed 14 years ago by James Burke

Resolution: invalid
Status: reopenedclosed

No test case. Closing this out. Feel free to open with a test case.

Note: See TracTickets for help on using tickets.