http://www.w3.org/Bugs/Public/show_bug.cgi?id=6777 --- Comment #15 from Henri Sivonen <hsivonen@iki.fi> 2009-04-06 15:44:36 --- (In reply to comment #14) > That > still wouldn't achieve compatibility of course - the only way to ensure that > the expression //p[namespace-uri()=''] continues to return the same result that > it does now is to map your HTML5 DOM to an XDM instance (or the XPath 1.0 > equivalent) in which the p elements are in no namespace. Since you're so > concerned about compatibility, I can't see why you are so reluctant to do that. That would address the backward-compatibility issue without addressing the forward-looking point of changing how HTML elements in the DOM are assigned to a namespace. The point of assigning HTML elements to the http://www.w3.org/1999/xhtml namespace is to make the data model representation consistent between the two serializations of HTML (text/html and application/xhtml+xml). So that in the future, authors can write XPath expressions with names in the http://www.w3.org/1999/xhtml namespace and those expressions work on DOMs regardless of whether the DOM came from text/html or application/xhtml+xml. -- 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:44:46 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 April 2009 15:44:46 GMT