131074 2014-04-01 16:03:57 -0700 document.createElement() should always return an element in the HTML namespace 2023-01-03 16:36:23 -0800 1 1 1 Unclassified WebKit WebCore Misc. 528+ (Nightly build) Unspecified Unspecified RESOLVED CONFIGURATION CHANGED P2 Normal --- 1 dbates webkit-unassigned ahmad.saleem792 ap bfulgham cdumez rniwa oldest_to_newest 996498 0 dbates 2014-04-01 16:03:57 -0700 According to <http://dom.spec.whatwg.org/#dom-document-createelement> (20 March 2014), document.createElement() should always return an element in the HTML namespace: [[ The createElement(localName) method must run the these steps: 1. If localName does not match the Name production, throw an "InvalidCharacterError" exception. 2. If the context object is an HTML document, let localName be converted to ASCII lowercase. 3. Let interface be the element interface for localName and the HTML namespace. 4. Return a new element that implements interface, with no attributes, namespace set to the HTML namespace, local name set to localName, and node document set to the context object. ]] At the time of writing, document.createElement() [1] returns an element in the HTML namespace for an XHTML document. Otherwise, it returns an element in the "null namespace". [1] <http://trac.webkit.org/browser/trunk/Source/WebCore/dom/Document.cpp?rev=166600#L854> 996866 1 dbates 2014-04-02 14:43:31 -0700 For completeness, I ran into this issue when merging a Blink patch in bug #131079. 1897884 2 ahmad.saleem792 2022-09-12 09:15:01 -0700 rniwa@webkit.org - Is this something still needed or an issue? Thanks! 1898006 3 ap 2022-09-12 14:33:51 -0700 Running this in Web Inspector console for a HTML webpage, looks like this is fixed. > document.createElement("a") < <a></a> > $1.namespaceURI < "http://www.w3.org/1999/xhtml" 1922746 4 ahmad.saleem792 2023-01-03 16:36:23 -0800 We have FIXME about this bug in here: https://github.com/WebKit/WebKit/blob/main/LayoutTests/resources/js-test.js#L19 Should we modify our js-test.js script to update this?