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

@oleersoy Once again, here you have something you can do with `is="my-template"` that you cannot achieve with regular `<my-template>`  http://jsbin.com/hagena/3/edit?html,output

@Zambonifofex 
>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.



They did so in 2.x, even though it confused quite many developers, produced new bugs, etc ;)
[AFAIK, they did so just to set their users free from polyfill](https://github.com/Polymer/polymer/tree/2.0-preview#v1-custom-elements)

I does not only look ugly, and unnatural. First of all, it does not solve the entire problem. Still, you end up with `<dom-if>` element in your tree, which is not inert, which is rendered as any other `<span>` - and that is something I try avoid. Needless to mention how messy, bug-prone and performance-expensive is proper 1-1 binding of parent and children, and making sure no external mutation to those elements breaks your functionality. 

-- 
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-259206701