Opened 13 years ago

Closed 12 years ago

#3441 closed defect (wontfix)

dojo.event.connect(myDiv, 'appendChild') causes TypeError in MSIE 6

Reported by: guest Owned by: sjmiles
Priority: high Milestone:
Component: Events Version: 0.4.2
Keywords: Cc: rhys@…
Blocked By: Blocking:



Connecting to a <div>'s appendChild method works beautifully in Firefox 1.5+. It causes an internal TypeError? in IE 6.0.2900.2180.xpsp.051011-1528. I've attached a step-by-step recreate that uses AOL's CDN to load dojo 0.4.3.

Ultimately I get---

DEBUG:  [TypeError: Object doesn't support this property or method] when calling appendChild$joinpoint$method on [object] with arguments [object Object]
FATAL exception raised: Object doesn't support this property or method

deep within the dojo source when I run Step 3 in the recreate.

This particular problem, combined with the container <div> in a DebugConsole? widget, can cause 100% spikes in the same version of IE. I found it because I was hooking the container <div> to prepend debug timestamps and provide automagic scrolling.

Attachments (1)

ConnectAppendChild.html (1.5 KB) - added by guest 13 years ago.
Full problem recreate

Download all attachments as: .zip

Change History (4)

Changed 13 years ago by guest

Attachment: ConnectAppendChild.html added

Full problem recreate

comment:1 Changed 13 years ago by sjmiles

Resolution: wontfix
Status: newclosed

TypeError?: Object doesn't support this property or method

Right. As far as I know, it's not possible to connect to IE built-in methods because of how IE implements them. Unless I am mistaken, this is not any defect in Dojo.

comment:2 Changed 12 years ago by guest

Resolution: wontfix
Status: closedreopened

No way to have an error thrown during, say if IE and a native method are detected? Some pre-emptive error checking on dojo's part would save others hours of debugging only to find out it's a known limitation.

comment:3 Changed 12 years ago by sjmiles

Resolution: wontfix
Status: reopenedclosed

The event code has been entirely reworked for 0.9, so we will have to review this problem in that context.

Note: See TracTickets for help on using tickets.