Re: [custom-elements-tests][html-templates-tests] Submission/unipro (#437) from sgrekhov on 2013-11-28 (public-web-platform-tests-notifications@w3.org from November 2013)

From: sgrekhov <web-platform-tests-notifications@w3.org>
Date: Thu, 28 Nov 2013 06:10:17 GMT
To: public-web-platform-tests-notifications@w3.org
Message-Id: <<web-platform-tests_issue_437_1385619017185@w3.org>>

This is an interesting point. Really, is the type of exception specified for this or not? Specification reads (definition construction algorithm, step 4) "If TYPE is an invalid custom element type, set ERROR to InvalidType and stop."

In fact now in Chrome "InvalidCharacterError" is thrown with the message "Failed to call 'register' on 'Document' for type 'xframe': : 'xframe' is not a valid name.". It's possible to check InvalidCharacterError here but will it be a cross-browser test in this case?

View on GitHub: https://github.com/w3c/web-platform-tests/pull/437#discussion_r7977569

Received on Thursday, 28 November 2013 06:10:23 UTC