- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 06 Apr 2009 16:04:59 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6777 --- Comment #18 from Henri Sivonen <hsivonen@iki.fi> 2009-04-06 16:04:59 --- (In reply to comment #16) > I think the tools you have to work with have already been identified - you have > control over the mapping to the data model, and you have control over the > default element namespace for queries. The data model approach would mean that you could never even in the future write unified XPath expressions for both text/html and application/xhtml+xml DOMs. As for the default namespace, if there's a way how I could hack the XPath 2.0 default element namespace behavior into an XPath 1.0 processor, I'd be interested in exploring that approach. Requiring the XPath 1.0 processor to be replaced with an XPath 2.0 processor entirely is not a feasible first step. How far away from approximating XPath 2.0 in the Compatibility Mode with http://www.w3.org/1999/xhtml as the default namespace would the result be if the check was: If the document is an HTML document and a name expression is being compared against an element, behave as if "" namespace on the expression side were the "http://www.w3.org/1999/xhtml" namespace. ? -- 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 16:12:50 UTC