Re: [xsl] XSLT 1.0 in browsers

[Michael Dykman <mdykman@xxxxxxxxx>]

I have been doing quite a lot of work in this area:  the simple answer
is: no.Few, if any mobile devices have support in the browser.

Most modern desktop browsers support it well:  IE (since 5.5 at least)
FireFox since 2.0, Chrome.  I had some trouble with Safari and am
doing server-side rendering for those devices..  that was awhile ago
and I can't remember what the issue was.

I use generated XSL 1.0 which is limited to a pretty tight core
vocabulary, all of which seems to be working perfectly in the wild but
my production code should not be considered full-blown XSL 1.0
coverage tests, so there may still be plenty of issues I haven't
observed.

 - michael dykman


On Wed, Sep 8, 2010 at 1:35 PM, Dimitre Novatchev <dnovatchev@xxxxxxxxx>
wrote:
> Good question. I would also like to know.
>
> A necessary addition -- what is the degree of compliance of a given
> browser's support for client-side XSLT processing.
>
> Even data beyond this may be very important: for example, does a
> particular browser-xslt-processor have its own xxx:node-set()
> extension or does it support EXSLT (which modules)?
>
>
> Ideally, we will have a table that has on one axis the different
> browsers and on the other axis the different features of interest.
>
>
> --
> Cheers,
> Dimitre Novatchev
> ---------------------------------------
> Truly great madness cannot be achieved without significant intelligence.
> ---------------------------------------
> To invent, you need a good imagination and a pile of junk
> -------------------------------------
> Never fight an inanimate object
> -------------------------------------
> You've achieved success in your field when you don't know whether what
> you're doing is work or play
>
>
>
>
> On Wed, Sep 8, 2010 at 10:28 AM, Max Toro <maxtoroq@xxxxxxxxx> wrote:
>> Is XSLT 1.0 supported in all browsers, including those that run on
>> mobile devices, video game consoles, internet-enabled television sets,
>> etc. ?
>> --
>> Max Toro
>
>



--
 - michael dykman
 - mdykman@xxxxxxxxx

 May the Source be with you.