- From: <bugzilla@jessica.w3.org>
- Date: Tue, 15 May 2012 12:45:36 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17058 --- Comment #7 from Nicholas Stimpson <nicholas.stimpson@ntlworld.com> 2012-05-15 12:45:36 UTC --- (In reply to comment #6) Yes, I think it would. But I see changing the way createElement works as pretty fundamental change for almost everyone who manipulates a XML DOM outside of a browser, and that's not really reflected in the goals section (which looks like a set of consolidation, simplification, correction, and extension changes, and therefore not very frightening.) I think it's important that developers know that that if they build a DOM with a DOM4 library, that they may well end up with a fundamentally different DOM to have to process. Particularly in places where DOMs contain a mixture of namespaced elements and elements in no namespace (I've certainly built those in the past), code that tests the element's namespace directly (via namespace-uri() in xpath for example) is liable to need to change. But if attributes are also completely different, then that's going to become pretty obvious quite quickly. -- Configure bugmail: https://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 Tuesday, 15 May 2012 12:45:46 UTC