Re: [w3c/webcomponents] Why must the is="" attribute exist? (#509)

I think I know what you mean. For example, search engines read the tag names from the markup in order to detect what type of content and how to render it in the search results. This point may be moot because today it completely possible to use a root `<app>` component with a closed shadow root. In this case a search engine might only ever see

```html
<html>
    <head>
        <title>foo</title>
    </head>
    <body>
        <app></app>
    </body>
</html>
```

That's functionally equivalent to an app with no shadow roots and made entirely of randomly named elements:

```html
<html>
    <head>
        <title>foo</title>
    </head>
    <body>
        <asf>
            <oiur>
                ...
            </oiur>
            <urvcc>
                ...
            </urvcc>
        </asf>
    </body>
</html>
```

Based on that, I don't think it's necessary to keep element names.

I imagine a couple remedies:

1. Allowing both forms and let users decide which to use: `<button is="awesome-button">` or `<awesome-button>` and let users decide which to use as they so wish.
1. Allowing overriding of native elements (which pairs well with the idea of [per-shadow-root element registrations](https://github.com/w3c/webcomponents/issues/488) as in "hey, let me define what a `<p>` element is within my component that has no paragraphs."). Then `<button>` could behave like `<awesome-button>`, and search engines or other tools would be able to receive the same semantic meaning. This idea only works if the elements are in Light 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-224146249

Received on Tuesday, 7 June 2016 02:16:45 UTC