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

There's been a lot of argument here about why some people like `is=""` and others don't, but I'd like to hear constructive suggestions from the anti-is side of how we can extend custom elements without using `is` while preserving all of the functionality of the native element and compatibility with browsers that don't support custom elements at all.

Consider this custom element:

`<a is="fancy-anchor" href="/something">Fancy Anchor</a>`

If `is=""` isn't an option, I'm assuming that the element would look like this:

`<fancy-anchor href="/something">Fancy Anchor</fancy-anchor>`

If that's the case, how does one implement it so all of the following are true?

- A screen reader can always recognize that it is a link to another page
- Clicking on the link opens `/something` when JavaScript is disabled
- `fancy-anchor`s can be focused using the tab key in IE8
- The script that defines fancy anchor can be loaded asynchronously
- A search engine will be able to tell that there is a link to `/something` on that page.

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