Subject: Re: [xsl] getting javascript into an xsl variable From: Michael Dykman <mdykman@xxxxxxxxx> Date: Tue, 28 May 2013 18:52:31 -0400 |
I have an experimental system that I and others have built some large applications on. It outputs XML with XSL processing instructions to be transformed in browser and have found no real limitations in what Javascript I can use. Anything I have thrown at it, including google ads, google map widgets, heavy-handed jquery usage or obscure widgets, anything that worked in the static context, has continued to work for me via XSLT-1.0 in-browser. On Tue, May 28, 2013 at 6:31 PM, Liam R E Quin <liam@xxxxxx> wrote: > On Tue, 2013-05-28 at 16:32 -0400, Michael Dykman wrote: >> By the time it has become >> executable as a script node in an HTML document, all memory of XSL >> origins are gone. > > Note also that there are restrictions on what JavaScript can happen in > HTML generated by XSLT in the browser, for reasons that elude me. > > Liam > > -- > Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ > Pictures from old books: http://fromoldbooks.org/ > Ankh: irc.sorcery.net irc.gnome.org freenode/#xml > -- - michael dykman - mdykman@xxxxxxxxx May the Source be with you.
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] getting javascript into a, Liam R E Quin | Thread | Re: [xsl] getting javascript into a, dan haig |
Re: [xsl] getting javascript into a, Liam R E Quin | Date | [xsl] Re: XSLT 3.0 Relax NG Schema, Xmlizer |
Month |