- From: <bugzilla@jessica.w3.org>
- Date: Tue, 20 May 2014 16:51:48 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25830 --- Comment #1 from Dimitri Glazkov <dglazkov@chromium.org> --- (In reply to johnjbarton from comment #0) > Two parts of the definition of Custom Elements conflict: > > http://w3c.github.io/webcomponents/spec/custom/#dfn-custom-element-type > "The custom element type identifies a custom element interface and is a > sequence of characters that must match the NCName production, must contain a > U+002D HYPHEN-MINUS character, and must not contain any uppercase ASCII > letters." > > http://w3c.github.io/webcomponents/spec/custom/#dfn-custom-element- > constructor > "All custom elements must be constructable with a function object, called > custom element constructor. " > > A name defined as containing a dash cannot be parsed as a function name in > JavaScript. Consequently the two definitions above prevent mocking of Custom > Elements in a way fully compatible with the standard. <_< ... Is the problem with the meaning of the word "identifies"? Where is the custom element type parsed into a function name in the spec? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 20 May 2014 16:51:53 UTC