You say that my "workaround" is the same:
but that is only true if
ah yes, in other words, what you said was right, and what I said was
wrong:-)
So, if I understand you correctly, when IE removes the path information
(base uri) of the XSLT when it becomes a DOM object, it is still
behaving conformant. Though I do find it a bit strange,
It conforms to _XSLT/XPath_ which says nothing about how the properties
of the input trees are determined. Whether the DOM spec (or javascript
spec or in similar server-side scenarios jaxp spec etc, specify what the
base URI of the in-memory object is would have to be answered by someone
who's read those specs more carefully than I have. (In some of the cases
listed above I haven't looked at all...)
David
________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.
This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs.
________________________________________________________________________
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--