[Bug 21258] [Explainer]: this spec seems extremely dev-oriented, rather than HTML-writing-people oriented

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21258

--- Comment #3 from Dimitri Glazkov <dglazkov@chromium.org> ---
(In reply to comment #2)
> although the "Instantiating Custom Elements" section is a bit hard to read;
> is omitting a constructor attribute permitted, in which case the JS engine
> will have built a global-scoped constructor with a sensible name for you to
> use, overridable with your own function if you need it? If so, no
> complaints. If the constructor element stays necessary, however, then I'd
> still suggest a spec change to allow for a
> default-global-override-if-you-need-to approach.

That's still unspecified. Feel free to file a bug against the custom elements
spec (https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/custom/index.html)
and make your opinion heard.

> A fair point; I filed this because of genuine fear that this was (in any
> way) a near final draft. Consider it a sign of distress (which I guess is
> the best adjective to describe the feeling I got ;)

You should totally help out. The intro doc (the one you're reading) was written
ahead of time as a lightpath toward the actual, concrete specs and
implementations. See
http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/1227.html for the
explanation.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 12 March 2013 20:59:20 UTC