Altova Mailing List Archives

[xsl] [XSL] XSL Browser Integration

From: Alain <alainb06@------->
Date: 9/13/2007 8:01:00 PM
Is there a normalised way, on a browser environment (eq. XSLT1.0) to 
access with XSL code:

- the full "current" URI (ex. :  the most interesting 
part being obviously the option string, here: x=12&y=15)

- users preferences such as : preferred languages (or the http header 
accept_language string, for internationalisation purpose)

- navigation items such as : referrer, history (tainted)

- computer environment : screen resolution, colour width, OS, browser, 
initial canvas size, etc...

Part of that might be accessible on Mozilla based browsers through calls 
like document("about:config") because it is XUL and so working with XML 
behind the scene. But that will not be a portable method and doesn't 
answer to all of the basic integration needs.

As of XSLT1.0, there are 3 normalised system data informations available 
through system_property() call :

- xsl:version

- xsl:vendor

- xsl:vendor-uri

that could allow browser-guessing, but does not either meet the basics 
integration needs.

Many thanks in advance.



These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.