W3C home > Mailing lists > Public > public-html-xml@w3.org > January 2011

Re: The interpretation of script

From: Kurt Cagle <kurt.cagle@gmail.com>
Date: Wed, 19 Jan 2011 08:58:35 -0500
Message-ID: <AANLkTik+2yryXrAHQaDGNPdx529OP=8oPBrSHVNA4k-M@mail.gmail.com>
To: Henri Sivonen <hsivonen@iki.fi>
Cc: public-html-xml@w3.org
>
> Actually, it is different. If there are no natively supporting UAs when
> authors start deploying JS shims, you can be pretty sure that when the
> legacy has accumulated for a couple of years, there are sites that fail to
> check for native support.
>
> If you were to check for native support of MusicXML in
> application/xhtml+xml today, what would you check? It's hard enough to check
> for MathML support.
>
>
Perhaps this points to a potential feature for HTML that could prove very
useful. In XSLT there's an XPath command called xsl:function-available()
which will return true if the named function is available on the system.
Perhaps something similar on the JavaScript side, e.g., feature-available(),
could be used to determine whether a given capability such as MathML is
actually supported on the system in question?
Received on Wednesday, 19 January 2011 13:59:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 19 January 2011 13:59:40 GMT