Re: [webcomponents]: Declarative Custom Elements Take Umpteen, The Karate Kid Edition from Erik Arvidsson on 2013-05-15 (public-webapps@w3.org from April to June 2013)

From: Erik Arvidsson <arv@chromium.org>
Date: Wed, 15 May 2013 14:38:12 -0400
To: Scott Miles <sjmiles@google.com>
Cc: Dimitri Glazkov <dglazkov@google.com>, Robert Ginda <rginda@chromium.org>, Elliott Sprehn <esprehn@gmail.com>, Daniel Buchner <daniel@mozilla.com>, public-webapps <public-webapps@w3.org>, Rick Waldron <waldron.rick@gmail.com>, Allen Wirfs-Brock <allen@wirfs-brock.com>
Message-ID: <CAJ8+GoiHzUA+bX1G3Qf=z4_qsbcozMe-W-u7Owx68Jn-w9w9pA@mail.gmail.com>

Walking the ancestors from document.currentScript is a start. Is that
sufficient or should we add a document.currentElement?

On Wed, May 15, 2013 at 2:34 PM, Scott Miles <sjmiles@google.com> wrote:

> As long as there is a way to access the <element> from the <script>, I'm
> good.
>
>
> On Wed, May 15, 2013 at 11:31 AM, Dimitri Glazkov <dglazkov@google.com>wrote:
>
>> Despite little love from Scott for the mischievous walrus -- }); --
>> proliferation across the Web, are there any other cries of horror that
>> I should be listening to? I am hankering to write this as a spec
>> draft. Yell now to stop me.
>>
>> :DG<
>>
>
>

-- 
erik

Received on Wednesday, 15 May 2013 18:39:03 UTC