- From: Brian Kardell <notifications@github.com>
- Date: Fri, 29 Dec 2017 17:05:41 +0000 (UTC)
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 29 December 2017 17:06:04 UTC
I'm not sure adding a class is either a very high barrier or actually even wonky in terms of 'current state of things'. For example, there is no way to select `HTMLHeadingElement` and apply a style to all of the tags based on that interface.... currently. In that particular case, there's been much discussion/proposals around what to do (deliberately exposed pseudo-classes for them is one way - if that's the answer, then adding a class is a real good approximation, another is for allowing author defined aliases so additional sorts of things are possible). I'm not entirely sure what the 'right' answer is, but this feels like a question about DOM/CSS more generally than web components specific to me. -- 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-354472453
Received on Friday, 29 December 2017 17:06:04 UTC