The problem with "true subclassing" of builtins is that browsers are architected around local name checks, not class (brand) checks. So if you have `custom-input`, most of the code in browsers (this includes default stylesheets, which don't even have a way to match based on class) will not see it as `input`, which defeats the entire point. That's why the `is=""` hack is there, as it preserves the local name. But that's also why it's a hack, to work around a faulty architecture. -- 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/725#issuecomment-360408455
Received on Thursday, 25 January 2018 09:22:12 UTC