Inside XSLT

Ok, the more I think about using XSLT inside a browser the more it
becomes clear that XSLT
is a good substitute for doing the type of things one used to do and
still does with javascript.

However, Browsers have given javascript access to read-only functions
inside Window.Navigator,
Window.Screen, Window.History, Window.Location, and Window.Document.

When inside XSLT the builder of a new or modified web page needs
access to this
same type of read-only information.

In my opinion, Browsers must start providing access to the same read-
only information
inside XSLT that is now available inside Javascript. Moreover, since
this information is already exposed to Javascript it would seem to be
a straight forward thing to provide functions to do the same thing
inside Javascript.

Note: Here I am not talking about access to the DOM but instead access
to the information that when in a browser is in some sense global to
the part of the DOM representing the XHTML of the page. XPath performs
the "read only DOM Functions" for the XHTML inside XSLT.

John Perkins