- From: <bugzilla@jessica.w3.org>
- Date: Tue, 04 Mar 2014 18:10:28 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24543 --- Comment #6 from Michael Kay <mike@saxonica.com> --- Actually, I think that given the separation of the "initial context item" (which I would like to call "global context item") used for initializing global variables, and the "initial input sequence" (which I would like to call something like "initial match selection") used for the apply-templates stylesheet entry point, the problem largely disappears. The rule is simply that the global context item will never be a streamed node. It's up to the API design to ensure this; if something like a StreamSource or File is supplied, the API will typically build an in-memory tree. There is no longer any interference with the "initial input sequence", except for a legacy API that tries to set both to the same thing. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 4 March 2014 18:10:33 UTC