- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Fri, 31 Jan 2025 22:02:38 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-gaps-1] Bikeshedding names for ways to break gap decorations`. <details><summary>The full IRC log of that discussion</summary> <TabAtkins> kbabbitt: [shows example]<br> <TabAtkins> kbabbitt: when you ahve a grid with spanning items<br> <TabAtkins> kbabbitt: differnet behavior authors might want<br> <TabAtkins> kbabbitt: i'mve assigned some names which i don't love, thus the issue<br> <TabAtkins> kbabbitt: one is "t intersection". the word..<br> <TabAtkins> kbabbitt: the property name is gap-rule-break<br> <TabAtkins> kbabbitt: three value<br> <TabAtkins> kbabbitt: first is "spanning-item". deco continues as far as it can until it hits a spanning itme or a t-intersection<br> <TabAtkins> kbabbitt: second is "intersection", rules break at every intersection<br> <TabAtkins> kbabbitt: third is "none", don't break at all just keep running across the grid<br> <TabAtkins> kbabbitt: looking for better names for first two<br> <TabAtkins> kbabbitt: one suggestion of long & short<br> <florian> q+<br> <TabAtkins> TabAtkins: so it continues thru the intersection rectangle if it has right of way, but stops short otherwise. in a 2-way intersection, both ccontinue thru<br> <fantasai> rule-skip: none | span | intersection<br> <TabAtkins> astearns: none | spanning-item | all<br> <TabAtkins> florian: maybe a fourth variant, close to spanning-item<br> <TabAtkins> florian: stop at the start of the gap that would lead into a spanning item. you continue up to the crossing rule, but no further<br> <TabAtkins> kbabbitt: that's controlled by a different proeprty<br> <iank_> q+<br> <astearns> ack lea<br> <astearns> ack florian<br> <TabAtkins> s/stop at the start/instead of stopping at the start/<br> <fantasai> ahhh, in that case maybe rule-break: never | spanning-item | always ...<br> <TabAtkins> kbabbitt: the property is gap-rule-offset, i've set it to 0 here to show the differences, but 50% would have it hit the crossing rule<br> <astearns> ack iank_<br> <TabAtkins> iank_: also, deco isn't stopping when it hits the item, it's when it hits the gap<br> <astearns> ack fantasai<br> <TabAtkins> iank_: so if block 1 [in the example] was small and din't fill th etrack, the rule would still stop at the gap intersection<br> <TabAtkins> fantasai: in the 50% case what if you want it up-to-but-not-cross? if they're semi-transparent you'll see the overlap, right?<br> <TabAtkins> astearns: probabyl different issuea bout drawing things<br> <iank_> `continuous` ?<br> <kizu> q+<br> <TabAtkins> florian: they're probalby seaprate unless a good name would resolve that<br> <TabAtkins> kbabbitt: i do think they're separate<br> <TabAtkins> kbabbitt: this is landmark where they begin to stop, then you can specify where in that space they stop<br> <fantasai> rule-break: never | item | always<br> <fantasai> rule-break: never | item | intersection<br> <fantasai> rule-break: never | item | cross<br> <TabAtkins> florian: even tho one is about landmark and the other is a numeric adjustment, while we're thinking about landmark may want to distinguish betwen stopping at the gap or at the rule<br> <TabAtkins> TabAtkins: i think we could handle that in either property<br> <astearns> ack kizu<br> <TabAtkins> kizu: in this example, i can image an author wanting two more options<br> <fantasai> rule-skip: none | item | cross<br> <fantasai> rule-skip: none | item | crosssing<br> <fantasai> rule-skip: none | item | intersection<br> <TabAtkins> kizu: in the 4-way cross, could want either vertical or horizontal to break<br> <TabAtkins> kizu: if you do image decos later, could want that<br> <TabAtkins> fantasai: I think a point is not just how deep in the intersection but if it's continuous<br> <TabAtkins> astearns: it's whether you have a continuous line or if they are segments<br> <florian> rule-break: [gap | rule] && [spanning | horizontal | vertical]<br> <TabAtkins> fantasai: right. they might meet at the intersection, so with a solid line you couldn't tell the difference<br> <TabAtkins> fantasai: but if they're not a solid line they coudl matter<br> <TabAtkins> kbabbitt: thanks for the suggestions, i got what i wanted<br> <TabAtkins> kbabbitt: I'll noodle on these<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11491#issuecomment-2628474329 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 22:02:39 UTC