#8814 closed defect (fixed)
overriding onmousemove etc. then connecting doesn't work
Reported by: | bill | Owned by: | bill |
---|---|---|---|
Priority: | high | Milestone: | 1.3 |
Component: | Dijit | Version: | 1.3.0b2 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
See test_deferredConnects.html for test case.
If you specify an onmousemove handler on initialization (or any deferred-connect event), and then later do a dojo.connect() on that handler, the dojo.connnect() won't be called.
Change History (4)
comment:1 Changed 12 years ago by
Owner: | set to bill |
---|---|
Status: | new → assigned |
comment:2 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:3 Changed 12 years ago by
comment:4 Changed 11 years ago by
Note: See
TracTickets for help on using
tickets.
(In [16926]) When specifying a deferred-connect handler (like onmousemove) as an initialization parameter, and then later doing a dojo.connect(), the connect wasn't working.
Problem was that the connection from the Widget.focusNode to Widget.onMouseMove() was incorrect; it connected to the actual function, rather than using the string "onMouseMove", so that the later dojo.connect() call, which replaces Widget.onMouseMove() with a dispatcher function, wasn't affecting what the Widget.focusNode connection was executing.
Fixes #8814 !strict.