[Bug 11090] New: Add a note about XSLT-created scripts

http://www.w3.org/Bugs/Public/show_bug.cgi?id=11090

           Summary: Add a note about XSLT-created scripts
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: hsivonen@iki.fi
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Please add text (note or normative; I don't care as long as it's there) about
XSLT-created scripts. There are three cases:
 1) <?xml-stylesheet?>-triggered transform.
 2) Using XSLTProcessor.transformToDocument
 3) Using XSLTProcessor.transformToFragment

In case #1, scripts created by the XSLT processor that transforms directly into
DOM nodes should behave like parser-inserted scripts in the sense that they
execute in insertion order. That is, inline and external scripts maintain order
relative to each other. (In principle, one would expect the XSLT processor to
be blocked upon a parser-blocking script, but in practice, the only known
implementation didn't actually block the XSLT processor--just executed the
scripts in order. Even if the spec said to block the XSLT processor, I doubt
we'd prioritize changing this.)

In case #1, if the XSLT processor transforms to a stream and the stream is
reparsed, the right thing happens.

I didn't yet test what the legacy behavior for cases 2 and 3 is.

(I so wish the spec had had a reminder about this a couple of months ago...)

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 19 October 2010 09:42:09 UTC