- From: Liam R E Quin <liam@w3.org>
- Date: Thu, 11 Oct 2012 15:35:03 -0400
- To: Jirka Kosek <jirka@kosek.cz>
- Cc: Paul Grosso <paul@paulgrosso.name>, public-xml-core-wg@w3.org
On Thu, 2012-10-11 at 20:51 +0200, Jirka Kosek wrote: > I think this is a way to go for now. Writing down tests for all edge > cases mentioned in comment 8 will take some time. And for some tests I'm > not completele sure what Ian is talking about (<script> and blocking). > > I'm willing to be volunteer for collecting and writing down these tests > so we can have more precise definition of XSLT browser interaction in > HTML 5.1. That's awesome. If they are talking about "new functionality", it'd be really really useful to document (1) passing params to xslt, and (2) invoking xslt from javascript, both of which are supported in browsers in various incompatible ways today. So the alternative of a separate document saying how XSLT, XML and Web browsers interact has some attractions. Yes, it goes beyond what XML Core or XSL have done in the past, but this sort of thing needs to be written down somewhere, and if browser authors are willing to make changes once there's a written spec, it could be a big help to XML users. On <script> and blocking - once a We browser reaches a <script> element it has to stop formatting/rendering the HTML Web page and go and fetch the script and run it; only then can it resume formatting. So I think the question is, if <?xml-stylesheet...?> is encountered, does the browser block, fetch the resource mentioned, and then continue? (I'm not certain this is the exact question, but it's the right area) 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
Received on Thursday, 11 October 2012 19:36:21 UTC