If he didn't report the bug here, nobody has looked into it. Repeat after me:
<whine> WE NEED A BUG TRACKING SYSTEM -- NOW! WE NEED A BUG TRACKING SYSTEM -- NOW! WE NEED A BUG TRACKING SYSTEM -- NOW! WE NEED A BUG TRACKING SYSTEM -- NOW! WE NEED A BUG TRACKING SYSTEM -- NOW! </whine> ----- Original Message ----- From: Assaf Arkin <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, February 04, 2000 3:51 PM Subject: Deferred Element Definition > Jason Crickmer has been running into a problem using the deferred DOM. > > Apparently with an entity defined as: > > <!ENTITY fname "Jason"> > > and a reference defines as <body>Hello &fname;,</body> the deferred > document generates a DeferredElementDefinition instead of a > DeferredElement or Element. > > ui.DOMTreeFull attempts to construct the tree and match the node type > based on an array, and since ELEMENT_DEFINITION_NODE is not part of the > node type it supports, it throws an array index out of bounds exception. > > Has anyone looked into this problem? > > arkin > > > -- > ---------------------------------------------------------------------- > Assaf Arkin www.exoffice.com > CTO, Exoffice Technologies, Inc. www.exolab.org >
