W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2013

Re: [webcomponents]: When <element> is having a bad time

From: Brian Di Palma <offler@gmail.com>
Date: Wed, 31 Jul 2013 18:09:46 +0100
Message-ID: <CAKkpDQSrMJKdUryRxuLaCQeyiuV7YPZPW4FUnyfaMwtENnzfTg@mail.gmail.com>
To: Dimitri Glazkov <dglazkov@google.com>, public-webapps@w3.org
The linking stage would be a stage where all that happens is the
registration of custom elements.
No custom element code would execute, there is no need to dereference
the parent prototype.
All that happens is the loading of resources.

ES6 modules are meant to handle dependencies, it's in their design.
So instead of depending on a global custom element you hope has been
loaded you can import a HTML module.
Referencing an unbound global variable will throw a SyntaxError.

ES6 modules will also have a linking stage.

https://gist.github.com/wycats/51c96e3adcdb3a68cbc3

On Wed, Jul 31, 2013 at 5:50 PM, Dimitri Glazkov <dglazkov@google.com> wrote:
> On Wed, Jul 31, 2013 at 9:23 AM, Brian Di Palma <offler@gmail.com> wrote:
>> Is it not possible to have a linking stage before a compile stage?
>
> Can you help me understand this idea? I don't quite get the
> definitions of "linking" and "compile" when applied to Web platform.
>
>> Or to use ES6 modules so that elements must import the prototypes they
>> inherit from or a SyntaxError is thrown?
>
> How do modules help here? Can you elaborate a bit?
>
> :DG<
Received on Thursday, 1 August 2013 09:20:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:12 UTC