20483 2012-12-21 20:27:44 +0000 [Templates]: Specify the behavior of XDM when encountering <template> element 2013-01-24 17:41:39 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED FIXED P2 normal --- 15476 1 rafaelw dglazkov adamk hsivonen tross public-webapps-bugzilla oldest_to_newest 80505 0 rafaelw 2012-12-21 20:27:44 +0000 XPath transforms used by XSLT during initial construction should traverse through template content, but direct XPath DOM API calls should not. (I need to do a fair bit more digging in the spec to be able to more accurately describe the problem and solution here). 80506 1 rafaelw 2012-12-21 20:31:48 +0000 Also, ensure that the output of XSTL, if it contains templates, is parsed correctly (i.e. template content *is* lifted and appended into the template content document fragment). 81093 2 rafaelw 2013-01-09 00:30:13 +0000 Ok. Looking at this more, I think I get it. Here's what I see. Henri, tell me if this is right: -XSLT output must produce DOM "as if" it were parsed by XML (i.e. template contents go through the "worm hole". This must be the case for XSLTProcessor as well. -XPath DOM queries DO NOT traverse through the "worm hole" -XSLTProcessor directives DO traverse through the "worm hole" when processing the "source" DOM. 81104 3 hsivonen 2013-01-09 07:54:38 +0000 (In reply to comment #2) > Ok. Looking at this more, I think I get it. Here's what I see. Henri, tell > me if this is right: > > -XSLT output must produce DOM "as if" it were parsed by XML (i.e. template > contents go through the "worm hole". This must be the case for XSLTProcessor > as well. > > -XPath DOM queries DO NOT traverse through the "worm hole" document.evaluate, that is. > -XSLTProcessor directives DO traverse through the "worm hole" when > processing the "source" DOM. Yes, looks right. 81972 4 rafaelw 2013-01-22 21:26:08 +0000 https://dvcs.w3.org/hg/webcomponents/rev/f33622c39c5e I'm reluctant to say anything about XDM directly here. I'm hoping this is sufficient. Henri, if you're not happy with this, can you please suggest some appropriate wording. 81985 5 hsivonen 2013-01-23 09:29:52 +0000 (In reply to comment #4) > https://dvcs.w3.org/hg/webcomponents/rev/f33622c39c5e > > I'm reluctant to say anything about XDM directly here. I'm hoping this is > sufficient. > > Henri, if you're not happy with this, can you please suggest some > appropriate wording. I'd say something explicitly about the XPath API and not talk about serialization, because XSLT doesn't operate on serialization and the template spec changes the relationship of the serialization and the tree. Also, I'd avoid "should" in non-normative text. Something like: <p><em>Non-normative note: XSLT processing ought to treat template contents as descendants of the template element in XSLT input and place the descendants of a template element into template contents in XSLT output. However, XPath evaluation using the XPath DOM API ought not to match on template contents.</em></p> 81986 6 hsivonen 2013-01-23 09:30:53 +0000 Oh, and why non-normative? Political reasons? It's an interop-sensitive statement after all. 82099 7 rafaelw 2013-01-24 17:40:55 +0000 Changed per Henri's suggestion. https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/templates/index.html#xslt-and-xpath 82100 8 rafaelw 2013-01-24 17:41:39 +0000 tony, note the changed language on this in the previous comment.