Re: [w3c/webcomponents] Interface/class-based selector (#719)

Yeah I'm not a browser implementor but that certainly sounds expensive for a rather esoteric feature. Possibly having it tied to the inheritance hierarchy at the time `.defineElement` is called? That doesn't feel too restrictive to *me*, but I'm just one person.

-- 
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/719#issuecomment-367197780

Received on Wednesday, 21 February 2018 02:57:49 UTC