- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Sat, 07 Dec 2013 08:00:39 -0500
- To: Dimitri Glazkov <dglazkov@chromium.org>, public-webapps <public-webapps@w3.org>
On 12/6/13 3:28 PM, ext Ryosuke Niwa wrote:
>
> On Dec 6, 2013, at 7:37 AM, Erik Arvidsson <arv@chromium.org
> <mailto:arv@chromium.org>> wrote:
>
>> 1. The parser does not know that it needs to use MyElement.@@create
>> to create the JS objects when it sees a <my-element>.
>> 2. No callbacks for enteredView, leftView and attributeChanged.
>> 3. It depend on the magic of document.createElement which is
>> circular. A better way would be to do `super('my-element')` or
>> something like that.
>>
>> I wish we could resolve these remaining issues.
>
> In fact, fixing these issues is a requirement for us.
I just noticed that yesterday Erik filed three Custom Element bugs but I
didn't receive an announcement about them:
* [Custom]: No way to pass parameters to constructor
<https://www.w3.org/Bugs/Public/show_bug.cgi?id=24018>
* [Custom]: No way to associate class/constructor function
<https://www.w3.org/Bugs/Public/show_bug.cgi?id=24019>
* [Custom]: A tag name should be associated with the constructor and not
the prototype
<https://www.w3.org/Bugs/Public/show_bug.cgi?id=24020>
Unlike other specs/components, new Web Components bugs are not announced
on public-webapps (although like all of WebApps' components, new Web
Components bugs are announced on public-webapps-bugzilla [which only has
5 subscribers]).
For consistency reasons, and to facilitate transparency, it seems like
all new Web Component bugs should be announced on public-webapps. Does
anyone object to that?
-AB
Received on Saturday, 7 December 2013 13:10:40 UTC