- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 Jan 2025 21:41:01 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-gaps-1] Computed value of column-rule-width with none|hidden style and lists of values`, and agreed to the following: * `RESOLVED: Do the above.` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> kbabbitt: now it's decorations<br> <TabAtkins> kbabbitt: first, there's some behavior defined in multicol where if column-rule-style is none|hidden, column-rule-width is 0<br> <TabAtkins> kbabbitt: i'm extending those properties to allow multiple values to allow alternating/etc<br> <TabAtkins> kbabbitt: how do we accommodate the multicol behavior?<br> <TabAtkins> kbabbitt: two beahvior<br> <TabAtkins> kbabbitt: one is, if there's exactly one value and it's non/hidden, width is 0<br> <TabAtkins> kbabbitt: two is, if it contains multiple values and they're *all* none/hidden, width computes to 0<br> <TabAtkins> kbabbitt: lean toward first just to minimize beahvior needed for back compat<br> <TabAtkins> astearns: what do we lose if we don't do 2?<br> <fantasai> TabAtkins: Very minor concern (agree 1 is probably better) -- when we have behaviors that depend on list of values, can trip over it<br> <fantasai> TabAtkins: once you add more values<br> <fantasai> TabAtkins: ways to work around it, e.g. repeat your style and alternate<br> <astearns> ack fantasai<br> <TabAtkins> fantasai: is this a case wher eth eused value of the affected liens are still 0, right? so this is just about computed value of the width property?<br> <TabAtkins> kbabbitt: yeah<br> <TabAtkins> fantasai: this isn't inherited, so people probabyl won't care<br> <florian> q?<br> <TabAtkins> TabAtkins: good argument for the discontinuity not mattering<br> <emilio> q+<br> <TabAtkins> fantasai: maybe we could even just change the multicol rule behavior, seems less likely for it to be something people are depending on it<br> <TabAtkins> kbabbitt: could do a stud<br> <TabAtkins> fantasai: probably not that important, but maybe good<br> <astearns> s/stud/study/<br> <TabAtkins> fantasai: i could imagine not computing to 0 behind useful so you could inherit to children. maybe that's too weird<br> <astearns> ack emilio<br> <fantasai> s/could/could explicitly/<br> <TabAtkins> emilio: on the one hand, existing behavior is consistent with outline-width and border-width<br> <TabAtkins> emilio: on the other hand, i'm not a fan of that behavior<br> <TabAtkins> emilio: so i have a slight preference to try and get rid of the weird behavior if we can<br> <TabAtkins> fantasai: the used value is always 0 regardless, this is just computed value<br> <TabAtkins> emilio: 'border' i doubt we could change, without changing gCS()<br> <TabAtkins> emilio: border used to be a "used value" property<br> <fantasai> s/changing/special-casing/<br> <TabAtkins> emilio: so we'd probably still need to special-case it if we wanted to get rid of this in general<br> <TabAtkins> emilio: common for people to just fetch the border-width and padding from gCS(), so needs to stay 0<br> <TabAtkins> emilio: but maybe could change outline as well<br> <TabAtkins> fantasai: what if we said hidden/none no longer affect border/outline/column-rule<br> <TabAtkins> fantasai: but gCS() returns 0 on these properties if the style is hidden/none<br> <TabAtkins> emilio: i think we could get away with that<br> <fantasai> s/affect/affect computed value of/<br> <TabAtkins> florian: problem is gCS() isn't computed value, it's "resolved value". Proposal is computed value doesn't set to 0, only resolved value. So inheritance sitll gets the proper value.<br> <TabAtkins> kbabbitt: so still a question of how we do that for gap-rule<br> <TabAtkins> TabAtkins: emilio suggested we can do this resolved-value hack only for border, just fix outline and column-rule ot normal<br> <TabAtkins> emilio: [outlines that]<br> <TabAtkins> emilio: we could add it into outline/column-rule for single values *if needed*<br> <TabAtkins> emilio: if you inherit the whole border it does what you want, if you inherit border-width of 0 and then reset border style, uh, why?<br> <fantasai> TabAtkins: So we remove the current to-zero computation for all these properties. Instead do it in gCS only for border-width only.<br> <fantasai> TabAtkins: If we need to, go back and apply for outline/column-rule if needed for compat<br> <TabAtkins> astearns: objections?<br> <TabAtkins> RESOLVED: Do the above.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11494#issuecomment-2628447227 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 31 January 2025 21:41:01 UTC