Re: [webcomponents]: Platonic form of custom elements declarative syntax from John J Barton on 2013-04-11 (public-webapps@w3.org from April to June 2013)

From: John J Barton <johnjbarton@johnjbarton.com>
Date: Wed, 10 Apr 2013 20:00:05 -0700
To: Dimitri Glazkov <dglazkov@google.com>
Cc: Rick Waldron <waldron.rick@gmail.com>, Daniel Buchner <daniel@mozilla.com>, Scott Miles <sjmiles@google.com>, Rafael Weinstein <rafaelw@google.com>, public-webapps <public-webapps@w3.org>, Blake Kaplan <mrbkap@mozilla.com>, William Chen <wchen@mozilla.com>, Boris Zbarsky <bzbarsky@mozilla.com>, Jonas Sicking <jonas@sicking.cc>, Steve Orvell <sorvell@google.com>
Message-ID: <CAFAtnWycU7TX2_Evr1E_ecxPar_NvZJ5VKB5x5TdAhOkFTht7A@mail.gmail.com>

On Wed, Apr 10, 2013 at 6:51 PM, Dimitri Glazkov <dglazkov@google.com>wrote:

> On Wed, Apr 10, 2013 at 6:38 PM, Rick Waldron <waldron.rick@gmail.com>
> wrote:
> > Everyone's answer to this should be "no"; changing the expected value of
> the
> > top level "this", in some magical way, simply won't work.
>
> Can you explain why you feel this way?
>

1) Because <script> has never done this before, so it better be compelling.
2) Because causing |this| to change by moving the <script> tag in the HTML
or adding a layer of elements etc seems likely to cause hard to understand
bugs.
3) Forcing the binding based on position is inflexible.

To be sure this is implicit-declarative vs explicit-imperative bias, not
evidence.

Oh, sorry you were asking Rick.
jjb

Received on Thursday, 11 April 2013 03:00:32 UTC