- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Apr 2018 09:20:56 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `getComputedStyle only supports ::before/::after`, and agreed to the following resolutions: * `RESOLVED: getComputedStyle for pseudo elements that are not slotted is supported.` * `RESOLVED: Throw in this case` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: getComputedStyle only supports ::before/::after<br> <dael> github:<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/2149<br> <dael> gsnedders: getComputedStyle takes a second arg we could pass a pseudo element. Spec desn't agree with impl. It only allows some pseudo and impl allow any.<br> <dael> gsnedders: What do we do when it's invalid?<br> <dael> TabAtkins: Seems that we should support first-letter and first-line, but I don't see why not all.<br> <dael> emilio: Except slotted<br> <dael> TabAtkins: Yeah. We do still want some sort of magic thing.<br> <dael> TabAtkins: Slotted is first case of a pseudo being an alias for 1 or more elements. Aliases wouldn't work from this sort of example.<br> <dael> TabAtkins: We should prob make a term for things like slotted and things not like slotted and say it works for all things in that category.<br> <dael> Rossen: Currently it should work for non-slotted pseudo elements.<br> <dael> TabAtkins: Yes.<br> <dael> TabAtkins: I need to make it into 2 categories where slotted is only one in the second currently.<br> <dael> Rossen: Reasonable. Other optinos or objections?<br> <dael> RESOLVED: getComputedStyle for pseudo elements that are not slotted is supported.<br> <dael> gsnedders: What to do given an invalid pseudo element? All browsers return a css style declaration. FF throws if you trya nd access a property, everyone else returns the element style declaration and ignores the pseudo element.<br> <dael> TabAtkins: Returning element styles is...there's no reason to do that. Throwing would be best.<br> <dael> gsnedders: Nothing does that. So can it be web compat?<br> <dael> TabAtkins: FF doesn't let you touch it. Unless there's code to getgCS and not do anything I suspect we can throw.<br> <dael> fremy: Empty strings?<br> <dael> gsnedders: Reasonable. I'd prefer try throwing.<br> <dael> TabAtkins: At gCS call time.<br> <dael> ???: incl slotted?<br> <dael> TabAtkins: Yeah.<br> <TabAtkins> s/???/ewilligers/<br> <dael> Rossen: Do we throw for non-elements?<br> <dael> emilio: Yes.<br> <dael> Rossen: So this is not different.<br> <dael> TabAtkins: We're trying to say do the same.<br> <dael> Rossen: I'm trying to align whatever we do in that situation we should do it for this situation<br> <dael> fremy: If people call getComputedStyle with a placeholder we'll throw.<br> <dael> emilio: blink claims to support all eleemnts at parse time which is weird.<br> <dael> fremy: [missed]<br> <dael> emilio: Does gCS webkit get a result now? I guess not.<br> <dael> fremy: They work in Edge and Chrome they return.<br> <dael> emilio: gCS in ::webkit-foo<br> <dael> fremy: I think that's why we returnt he element style. People do random things we don't support and since Chrome does something we do something.<br> <dael> fremy: I'm fine saying we should throw but I won't be first to impl.<br> <dael> Rossen: In terms of defining behavior the most sensible thing is throw.<br> <dael> Rossen: Objections to that proposal?<br> <dael> RESOLVED: Throw in this case<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2149#issuecomment-380386188 using your GitHub account
Received on Wednesday, 11 April 2018 09:21:30 UTC