logo       

Re: [xmlc] 2.3beta getElementById() behavior: msg#00024

java.enhydra.xmlc

Subject: Re: [xmlc] 2.3beta getElementById() behavior

I knew pasting my options.xmlc in there would help!  :-)

On Jan 25, 2007, at 6:01 PM, Jacob Kjome wrote:

1.  Should it be expected that importNode()/adoptNode() register attributes that

were of type "ID" in the source document with the destination document?  I've

asked this question on the Xerces user list and am awaiting a response.


Yes.  But I'm biased.

2.  No matter the outcome of #1, should the XHTML DOM provide the same fallback

mechanism that the HTML DOM has, allowing lookup to succeed, albeit with

decreased performance than lookups of Ids that were originally in the

destination document at parse time?


Yes.  For all the same reasons that it's in the HTML DOM.

Which of these issues do you have control over and which do you have to convince Xerces to implement?

BTW, the XHTML DOM implements the HTML DOM interfaces.  I suggest you use those

interfaces rather than the XHTML interfaces.  It will make you code more

generic.


Yes, I know.  It's a mistake that I have yet to correct.  I never plan to use non-XML-compliant HTML code, but I agree that using the more generic interface would make my code better.

Erik

--
You receive this message as a subscriber of the xmlc@xxxxxxxxxxxxx mailing list.
To unsubscribe: mailto:xmlc-unsubscribe@xxxxxxxxxxxxx
For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise