- From: Simon Pieters <simonp@opera.com>
- Date: Wed, 03 Apr 2013 23:23:10 +0200
- To: "Scott Miles" <sjmiles@google.com>
- Cc: "Dimitri Glazkov" <dglazkov@google.com>, "Anne van Kesteren" <annevk@annevk.nl>, public-webapps <public-webapps@w3.org>, "Elliott Sprehn" <esprehn@gmail.com>, "Angelina Fabbro" <angelinafabbro@gmail.com>, "Brian Kardell" <bkardell@gmail.com>, "Steve Orvell" <sorvell@google.com>, "Ryan Seddon" <seddon.ryan@gmail.com>, "Ladislav Thon" <ladicek@gmail.com>, "Dominic Cooney" <dominicc@google.com>
On Wed, 03 Apr 2013 09:55:33 +0200, Scott Miles <sjmiles@google.com> wrote:
>> Why don't we use <script> as the mechanism to import a component?
>
> One of the primary advancements of Custom Elements spec lies in the
> ability
> to combine HTML (templates), scoped CSS, and JavaScript into
> encapsulations. General HTML markup is an ideal vehicle.
>
> Specific syntaxes are still under debate, but this is the kind of thing
> we
> do using the polyfills:
>
> <element name='x-bundle-of-awesome'>
> <template>
> <style>
> /* scoped to this element */
> </style>
> <!-- Shadow DOM markup -->
> </template>
> <script>
>
> // this === <element>
>
> this.register({ /* controller prototype */});
> </script>
> </element>
I don't understand how the above answers my question.
--
Simon Pieters
Opera Software
Received on Wednesday, 3 April 2013 21:23:48 UTC