Dick Deneer <[EMAIL PROTECTED]> wrote on 12/24/2005 08:27:51 AM: <snip/>
> > > > Anyhow, there's really no need for the LSParser to support the > > current-element-node property. When there's an error, the DOMError > > reported to your error handler should contain the related node in the > > DOMLocator. > > I think this does not work like expected. In the normalizeDocument it > is ok. > But during a normal parse you only get linenumbers etc. The related > node always gives null. > So may be this is a real bug. You can just run the program to see it > yourself. Hmmmm... you're right. There's no code to support it in the LSParser implementation. That's probably an oversight. Assuming this was working you would always receive the parent of the node that would have been reported from a call to normalizeDocument(). This is because the validators sit in front of the DOM builder in the pipeline. The "related node" doesn't exist when the error is reported so the best we could do is report its parent. > Regards and have a nice ChristMas > Dick Deneer Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
