Bug 100802 - DOM Living Standard: document.createElement(null) should return <null></null>
Summary: DOM Living Standard: document.createElement(null) should return <null></null>
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL: http://dom.spec.whatwg.org/#dom-docum...
Keywords: WebExposed
Depends on:
Blocks:
 
Reported: 2012-10-30 17:48 PDT by Syoichi Tsuyuhara
Modified: 2022-08-05 11:51 PDT (History)
4 users (show)

See Also:


Attachments
screenshot (17.24 KB, image/png)
2012-10-30 17:48 PDT, Syoichi Tsuyuhara
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Syoichi Tsuyuhara 2012-10-30 17:48:47 PDT
Created attachment 171560 [details]
screenshot

According to DOM Living Standard, createElement's parameter is "localName", not "tagName".
>Element createElement(DOMString localName);
http://dom.spec.whatwg.org/#document

Firefox 19.0, Opera 12.10 follow this.

Firefox 19.0:
http://cache.gyazo.com/1c59a1170dc1aa21e600827c35a7cfc0.png
https://bugzilla.mozilla.org/show_bug.cgi?id=802562
https://hg.mozilla.org/mozilla-central/rev/9ddc62d965dc

Opera 12.10:
http://cache.gyazo.com/f0cc0bcd8b9b364d07bfbcb9f4984a45.png

But WebKit r131444 throws Error.
Comment 1 Ahmad Saleem 2022-08-05 11:51:12 PDT
Safari passes all WPT Tests for createElement including null cases.

https://wpt.fyi/results/dom/nodes/Document-createElementNS.html?label=master&label=experimental&aligned&view=subtest&q=createelement

Marking this as "RESOLVED COFIGURATION CHANGED". Thanks!