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

>   * you're able to show a form before the component is asynchronously loaded
>  * you re able to chose a select before its component is asynchronously loaded

These two would result in a flush of contents, and would be very confusing for users.

>  * you are able to compose web components through their Promise based API and load them on demand without blocking most basic features of the Web already compatible with every browser and screen reader and gaming console as well as spaceships
>  * you are able to offer a basic functionality that enables users before they'll have some JavaScript error because the Custom Elements wasn't transpled properly

To make these things possible, each web page needs to be written that doesn't assume that custom elements are always available. Given people don't write code whereby which they deal with js files being asynchronously loaded in arbitrary order beyond just waiting for all or a few large set of scripts being available to do work, I have mega doubts about this materializing in practice.

Do you have any examples of a large Web app in which they can continue to function while some or all custom elements have failed to load?

>  * you are able to ignore Custom Elements if these add non essential values to the already available native component in emergent markets with poor 2G connections and not much data
>  * you are able to promote at distance anything already semantically understood from the browser

Browsers would not be able to do this because in practice, the assistive technology looks at what's rendered to the screen (CSS box model), not DOM.

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