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

@oleersoy I'll answer by _not_ specifying the exact markup, because remember, we're trying to get to the answer without prescription

Ideally, the markup should:

- leverage the existing semantic markup and conventions devs use today, which other services rely on for all sorts of things

- not require review of code from different contexts to understand what native APIs the markup offers

- be as simple as possible for devs to write and reason about, while fulfilling the two basic conditions above

After you examine developer needs and optimal ergonomic configurations, it seems you'd want the combination of a native tag + some unique indication of its custom element nature.

So you tell me, what does that logically reduce to?

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