Re: [w3c/webcomponents] Polymer encouraged incorrect document.createElement() usage (#544)

So the status quo is that both Chrome and Firefox allow a string argument here still and I don't see any effort toward changing that.

* https://searchfox.org/mozilla-central/source/servo/components/script/dom/webidls/Document.webidl#36
* https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/dom/Document.idl?q=Document.idl&sq=package:chromium&dr&l=197 (note that rather than making the argument optional, this is an overloaded method; I suspect it doesn't affect undefined handling though due to the dictionary)

Firefox will simply ignore the second argument if it's a string. I'm going to change the DOM Standard to align with that.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/544#issuecomment-366655679