Re: Custom Elements: is=""

• From: Mark Giffin <m1879@earthlink.net>
• Date: Mon, 15 Jun 2015 09:40:03 -0700
• To: public-webapps@w3.org
• Message-ID: <557EFFE3.3030802@earthlink.net>

On 6/12/2015 11:19 PM, Anne van Kesteren wrote:
> On Fri, Jun 12, 2015 at 7:41 PM, Léonie Watson
> <lwatson@paciellogroup.com> wrote:
>> Is there a succinct explanation of why the is= syntax is disliked?
> Rather than
>
>    <button is=my-button></button>
>
> you want
>
>    <my-button></my-button>
>
> that just gets all the <button> goodness through composition/inheritance.

When I first learned about web components, the biggest disappointment 
for me was learning that if I wanted to base my new custom element on a 
native element like <button>, I could no longer have a custom tag name. 
So instead of having <my-button>, I had to use the funky and awkward 
<button is="my-button">. I realize there are good reasons for this, but 
it's very disappointing because it "broke" my idea of custom elements. I 
created a pull request for this in the Drawbacks section of the summary doc.

Mark

Received on Tuesday, 16 June 2015 13:38:50 UTC