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

@dglazkov I agree with @smaug---- that throwing breaks badly libraries and site that already bet on what html5rocks and all documentation around Custom Elements 'till now promoted. I wouldn't throw and if it's easier for developers to use new second argument, it's even easier for you to keep what's there already and warn instead.

Regardless, the reason my polyfill supports both is to indeed help developers migrating to the new V1 API so if blink will start throwing, I'll catch that, and switch blink to a polyfilled blink which would be inconvenient for everyone.

WebSQL is still there and it worked well for many, same goes for Custom Elements V0, imo.
𝄞 _Please don't throw_ ♩♫♬

-- 
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-241573625