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

@WebReflection, I wasn't intending to be tedious. I didn't/don't see the other posts you referenced and was only suggesting `<noscript>` be used for developers to explicitly provide the fallback for custom elements instead of the browser trying to determine a replacement.

Sorry it didn't provide a solution to the other problem you mentioned. Hope you get it figured out.

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