- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 06 Apr 2009 15:30:02 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6775 --- Comment #6 from Henri Sivonen <hsivonen@iki.fi> 2009-04-06 15:30:02 --- (In reply to comment #5) > >In any case, this needs to be triggered on the output method even though it is a DOM-to-DOM transform. > > Well, I don't think there's anything to stop you defining a process called say > H5Transform which takes an XSLT stylesheet, processes the source document as > defined in the XSLT specification, and then does some further processing on the > result tree based on what you find in the xsl:output definition. That wouldn't > require any changes to XSLT, and you could do it without waiting for a new XSLT > release. You could even define it using XSLT 1.0 rather than 2.0 as the > baseline. Would it be OK to do this in a deliverable of the HTML WG or the Web Apps WG? As noted in previous comments, regardless of which namespace HTML nodes are assigned, DOM-to-DOM transform in a browser with method='html' needs to deviate from the XSLT 1.0 spec by ASCII-lowercasing the local names in order to be compatible with existing content, so at least that behavior needs a specification home. > >I think this the XSLT spec should specify this behavior. > > I don't. OK. -- 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 Monday, 6 April 2009 15:30:11 UTC