- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 Mar 2021 16:18:47 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[Cascade / Pseudo-elements / Values / Fragmentation] currentColor when fragments have different colors`, and agreed to the following: * `RESOLVED: The return value of gCS to match FF behavior that first-line is ignored in gCS` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [Cascade / Pseudo-elements / Values / Fragmentation] currentColor when fragments have different colors<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/1510<br> <fantasai> https://github.com/w3c/csswg-drafts/issues/1510#issuecomment-803203212<br> <emilio> grr, webex interface is confused about whether I'm muted because Linux is confused about what mic I'm using, fantastic :(<br> <dael> fantasai: We discussed what to do when an element is frag so it has different parentage. span split between first and 2nd line and there's a first-line pseudo. Decided on inheritance and a bunch. Resolved currentColor or em or resolved per fragment<br> <dael> fantasai: FF has impl this based on test cases in issue. Edited in<br> <dael> fantasai: Don't have answer when you call API like gCS on the element. Has one style per element. Proposal is define the API which assume single value per box must ignore effect of non-tree abiding elements<br> <Rossen_> q?<br> <dael> fantasai: Means span split across 2 lines pretends first-line pseudo is not there. You don't have to compute differently if have broken across lines. Seems to be what FF is doing<br> <dael> fantasai: Want to run past WG<br> <dael> Rossen_: Proposed behavior is similar to that of first-line for gCS?<br> <dael> fantasai: Talking about defining the case of first-line for gCS<br> <dael> Rossen_: Rephrase: if you have an inline item that has a spec line-height and you do gCS and that line item has a number of fragments, one if first and one in second. gCS will return the first. Perhaps line-height isn't good example. What returns used values<br> <dael> TabAtkins: Color<br> <dael> Rossen_: What would color return?<br> <dael> fantasai: Color it will ignore the first-line style. First line is blue, span on 2nd line and it's black. Span splits it returns black. Span on the first-line still returns black. That way browser doesn't have to take into effect if the span breaks. We ignore first-line styles<br> <dael> fantasai: Could say take style of first box fragment. That's another possibility<br> <dael> Rossen_: Okay, makes sense. Thank you<br> <dael> Rossen_: Any feedback?<br> <dael> Rossen_: If not we can call for objections<br> <dael> oriol: Concern is usually cascade is in element tree and this is in fragment tree. Given display:contents you can have elements w/o fragments in frag tree. not clear it's well defined. Might be outside of scope of the issue. It may need extra work in the future in another issue<br> <dael> Rossen_: Thanks oriol<br> <dael> fantasai: Either way we need an answer for what gCS returns<br> <dael> Rossen_: Prop here is have the same behavior as FF and as you described for color?<br> <dael> fantasai: Yep<br> <dael> fantasai: 2 things that could make sense. Returnt he styles ignoring first-line. Other is return style of first fragment. FF has impl first option so we propose that.<br> <dael> Rossen_: Impl PoV this is easier. User PoV these are equally wrong since you don't have per frag access. For consistency sake with current impl I'm in favor of that proposed behavior<br> <dael> Rossen_: Not hearing other proposals. Objections to resolve return value of gCS to match FF behavior that first-line is ignored in gCS<br> <dael> RESOLVED: The return value of gCS to match FF behavior that first-line is ignored in gCS<br> <dael> Rossen_: Anything else on this?<br> <dael> fantasai: Just need to fold in edit<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1510#issuecomment-811191452 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 31 March 2021 16:18:49 UTC