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

> Reason 1 : People don't always live in Cities where internet is a basic need. 

If you are designing for these cities then keep it light weight.  The `is` attribute is not light weight.  By using is you are implying that you will be pulling in additional javascript to support the implementation of what the `is` attribute is targeting.  Thus your page will flicker as the elements are being upgraded and the user will end up having a poor experience.  In other words the `is` attributes guarantees that your comment: 

> If the default behaviour is not set then what they see when page loads will be some spaghetti half eaten.

Will be true.

>  I use 100 different buttons in a page, almost every actionable item is a button, round button , rect button , elliptical button etc ... 

These are all CSS core concerns.  You can do these without the `is` attribute and you will have a cleaner design.  Use SUIT-CSS, BEM conventions, etc.

The `is` attribute could also cause your maintenance and user experience support scenarios to turn into a nightmare.

A lot of companies are afraid to touch their CSS because the way they went about implementing it resulted essentially in a stack of wine glasses.  None of the glasses can be touched without fear of the entire stack tumbling.  You risk the same thing with the `is` attribute.








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