Re: L3 LS: Configuration parameter to enable/disable application specific DOM

>In that case, I agree that your proposal makes sense. But I have to ask:
>Won't _any_ parser that's capable of "smart" parsing necessarily contain
>a heavy dose of implementation-dependent features? It seems to me that
>an application-specific DOM tree that doesn't actually do anything isn't
>much more use than a generic DOM tree.
>  
>

When executing script in an XHTML page or SVG image, your only available 
parser might be the browser viewing the document and getting a generic 
DOM tree might be exactly what you want.  However, without a 
configuration parameter, the implementation has no way of knowing that.

Received on Monday, 5 January 2004 00:56:55 UTC