Re: [webcomponents]: Of weird script elements and Benadryl

@Erik - I think the real irony here, is that people probably will be using
an HTMLElement base quite often that simply adds new methods, scoped
styles, and a template - and they will come to loath the unnecessary
boilerplate (which also makes imperative library wrapping painful). I guess
this harkens back to my distaste for dropping an unnecessary cognitive ACME
anvil on developers who don't want to chase Roadrunner in the first place.

Meep Meep!

On Fri, Apr 12, 2013 at 3:06 PM, Erik Arvidsson <arv@chromium.org> wrote:

> On Fri, Apr 12, 2013 at 5:54 PM, Daniel Buchner <daniel@mozilla.com>wrote:
>
>> @Rick - when you say "see above", to what are you referring? IMO we
>> arrive at our intended outcome without introducing <script> scoping or
>> attribute issues, and at the same time reducing boilerplate, with the
>> following:
>>
>>
>> <element tagname="x-foo" inherits="SVGElement">
>>   <template>...</template>
>>   <script>
>>       XFooElement.prototype.bar = function(){...}
>>       XFooElement.prototype.readyCallback = function(){...}
>>   </script></element>
>> </element>
>>
>>  Where am I going wrong here?
>>
>
> DRY. Remember that we want to end up with ES6 class syntax so having to
> specify inherits as an attribute and extends in the class syntax does not
> seem good.
>
> --
> erik
>
>
>