27456 2014-11-27 19:02:11 +0000 Redefine Node.isDefaultNamespace(), Node.lookupNamespaceURI() and Node.lookupPrefix() 2016-04-18 17:47:20 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified PC Windows NT RESOLVED WORKSFORME P2 normal --- 1 crimsteam annevk ayg mike philipj www-dom public-webapps-bugzilla oldest_to_newest 115630 0 crimsteam 2014-11-27 19:02:11 +0000 Current definitions of this methods: http://dom.spec.whatwg.org/#dom-node-isdefaultnamespace http://dom.spec.whatwg.org/#dom-node-lookupnamespaceuri http://dom.spec.whatwg.org/#dom-node-lookupprefix don't cover any implementations. I'm mention about this situation in bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1061578 Question is: - what they should doing to be useful for devs - what is their actual usage; can be modify without breaking something (or even remove if usage is close to 0). This method has been introduced by DOM Level 3. It does not look good when the description in actual DOM does not match at least one implementation. 122400 1 philipj 2015-08-03 12:33:12 +0000 Can you summarize what you think the spec should say and, if you have time to figure it out, how that would differ from what is implemented in Blink today? There are no use counters for these methods, but I could add some if there's any non-trivial change suggested. 122460 2 crimsteam 2015-08-04 22:53:23 +0000 Aditional bugs from Mozilla: https://bugzilla.mozilla.org/show_bug.cgi?id=312019 https://bugzilla.mozilla.org/show_bug.cgi?id=505178 BTW, this example https://bugzilla.mozilla.org/show_bug.cgi?id=312019#c17 still was not correct, so Firefox behaviour is opposite to IE and Chrome behaviour even in such small things. Old algorithms for this methods from DOM3: http://www.w3.org/TR/DOM-Level-3-Core/namespaces-algorithms.html New DOM is more simple and some other stuff which operate on namespace was kicked (like Document.normalizeDocument): http://www.w3.org/TR/DOM-Level-3-Core/core.html#Document3-normalizeDocument To be honest I have no idea what you can do with it. I never use this methods so try find some other usage cases but without satisfactory results. Most libraries for DOM don't use them, all other examples try operate on namespace:element by other way (iterate and directly checking element/attr properties, using CSS selector, etc.). I try figure out how they are implemented in browesers, but realy, this was the worst in all DOM. I get different result in all browsers for HTML, when testing *XML (via DOMImplementation) get another differences, even for innerHTML:) I guess that because we have these differences no one uses these methods. Maybe Jonas Sicking or Henri Sivonen (via https://bugzilla.mozilla.org/show_bug.cgi?id=505178#c10) could suggest some practical applications for them if they must stay in new DOM spec. Are there any data on their usage? And of course remember that this methods came from Node, so again may be a potential problem for Attr, because they jump to owner Element (if exist), and who knows if devs don't use them directly in attributes. Currently all browsers still have them for Attr. 122464 3 philipj 2015-08-05 10:56:14 +0000 There aren't any use counters for these in Blink, but I had a look in the 20150101 httparchive dump, and the regex 'lookupPrefix|lookupNamespaceURI|isDefaultNamespace' only matches in 453 of 10139623 resources, which is ~0.0045~. Still, given how old these APIs are, I don't think that's low enough to just remove them, but it does mean we don't need to worry a lot about edge cases. 125841 4 ayg 2016-04-14 13:16:27 +0000 Testing <http://w3c-test.org/dom/nodes/Node-lookupNamespaceURI.html> in Firefox, Chrome, and IE 11 shows that all fail a number of tests, but there's no single test that all three fail. This suggests that the current spec is probably good enough to implement, given the marginal use of the feature. (All three browsers pass all the lookupPrefix tests. I didn't check to see how thorough the tests are or inspect Gecko source code to see whether we deviate significantly from the spec.) 125859 5 crimsteam 2016-04-14 16:30:07 +0000 Aryeh Gregor check this: <script> var newDiv = document.createElementNS("www.test.com", "ns:div"); var newTest = document.createElementNS("www.test.com", "test"); var newP = document.createElement("p"); newDiv.appendChild(newTest); newDiv.appendChild(newP); console.log(newDiv.namespaceURI + " | " + newDiv.prefix); // www.test.pl | ns console.log(newTest.namespaceURI + " | " + newTest.prefix); // www.test.pl | null console.log(newP.namespaceURI + " | " + newP.prefix); // http://www.w3.org/1999/xhtml | null console.log(newDiv.lookupPrefix("www.test.com")); // ns console.log(newTest.lookupPrefix("www.test.com")); // ns console.log(newP.lookupPrefix("www.test.com")); // ns </script> Chrome: ns, ns, ns << per DOM this looks correct Firefox: null, null, null IE and Presto: ns, null, ns "This suggests that the current spec is probably good enough to implement, given the marginal use of the feature." << yep, if finally some engine implements all of these guidelines, then changes in the spec will not necessarily. 125888 6 ayg 2016-04-18 17:47:20 +0000 The spec seems fine, although browsers are not yet interoperable. Reopen if there's a specific change you'd like in the spec (or, better, file a GitHub issue).