Re: [w3c/webcomponents] The is="" attribute is confusing? Maybe we should encourage only ES6 class-based extension. (#509)

By the way, I agree that `is` looks horrifying, and is very counter‐intuitive. Everyone agree it’s a hack. In fact, you’ll see me arguing against them the same way you are earlier in this thread. Maybe if we did everything from scratch, we wouldn’t need `is`, but as it stands, it’s very necessary. Besides being useful for the progressive enhancement: if I have a `button type="submit" is="my-button"` it will act like a regular submit button if either the browser doesn’t support custom elements, or if the user has JavaScript disabled.

> Is there something that you can do with juicy-template that you cannot do with a web component?

Well, I’m not sure about `juicy-template`, but Polymer has “if”s and loops. They *could* have done `<dom-if><template>` instead of `<template is="dom-if">` but that looks ugly, and feels very unnatural.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/509#issuecomment-259172056