If 'is' is not null and custom element definition not found, NotFoundError should be thrown |
||
Issue description
Version: Latest
OS: Ubuntu 14.04
What steps will reproduce the problem?
<!doctype html>
<script>
var XButton = document.registerElement('x-button', {extends: 'button'});
var elem = document.createElement('button', {is: 'x-button'});
console.log("check: " + (elem.constructor === XButton));
try {
elem = document.createElement('button', {is: 'unknown'});
} catch (NotFoundError) {
console.log("check: " + (elem.constructor !== XButton));
}
</script>
What is the expected output?
Both checks pass, NotFoundError should be thrown
What do you see instead?
One check pass
Please use labels and text to provide additional information.
https://dom.spec.whatwg.org/#dom-document-createelement, step 4 "If is is non-null and definition is null, then throw a NotFoundError." should be implemented.
,
Jan 19 2017
Hi, as discussed, probably we don't need this for V0 elements since the spec describes the behavior for V1 only. If it is OK with you guys I will close this bug as WontFix.
,
Jan 20 2017
Thank you for filing this and following up. |
||
►
Sign in to add a comment |
||
Comment 1 by dominicc@chromium.org
, Nov 8 2016