- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Feb 2023 00:33:13 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-overflow-3][css-overflow-4][css-overflow-5] Reshuffling Levels`, and agreed to the following: * `RESOLVED: Move line-clamp stuff from Overflow 3 to 4` * `RESOLVED: Move the continue:fragments to an appendix, marking it as unstable.` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> fantasai: florian and i wanted to prepare Overflow 3 for CR<br> <TabAtkins> fantasai: We'd like to shift the line-clamp stuff to L4<br> <TabAtkins> fantasai: Also anything else that's not already in 2 browses<br> <TabAtkins> fantasai: And then shift the overflow-fragments stuff from L4 to L5<br> <TabAtkins> fantasai: Also, there's some extensions to text-overflow in L4 - do we want to keep it there or push them to L5?<br> <TabAtkins> fantasai: q to the WG<br> <fantasai> -> https://drafts.csswg.org/css-overflow-4/#text-overflow<br> <TabAtkins> florian: I'd just move the "keep" fragment stuff to L5<br> <TabAtkins> florian: The text-overflow stuff was in CSS UI for a decade+... impl is lacking but the stability is good. Not nearly as compliated as the rest<br> <TabAtkins> florian: So move "continue: fragments" to L5, move line-clamp to L4, keep the rest as-is<br> <TabAtkins> Rossen_: The L3 to L4 makes sense to me<br> <TabAtkins> Rossen_: Not sure what moving to L5 buys us for now.<br> <TabAtkins> Rossen_: ARe we expecting L4 to advance fast?<br> <TabAtkins> florian: good question, the continue:fragments stuff is a continuation on line-clamp. If we keep line-clamp as it is, the *next* thing is continue:fragments<br> <TabAtkins> florian: So if we keep it as is, c:f will make sense, but if we don't, it probably won't make sense to keep around.<br> <TabAtkins> fantasai: and continue:fragments is very experimental and complicate<br> <fantasai> TabAtkins: I'd rather push to an appendix<br> <TabAtkins> florian: that works too<br> <TabAtkins> florian: It's less helpful for issue triage, github labelling<br> <TabAtkins> florian: But in terms of spec, whichever<br> <TabAtkins> fantasai: continue:fragments is on the level of CSS Regions in terms of CSS layout.<br> <TabAtkins> fantasai: Just don't think it's not a great idea<br> <TabAtkins> Rossen_: Think we should do the resolutions separately<br> <TabAtkins> Rossen_: So objections to moving line-clamp to L4?<br> <TabAtkins> [no objections<br> <TabAtkins> RESOLVED: Move line-clamp stuff from Overflow 3 to 4<br> <TabAtkins> florian: Having done that, I'm opposed to keeping continue:fragments in the main body<br> <TabAtkins> florian: I have a pref for l5 for triage purposes<br> <fantasai> TabAtkins: I don't like having single-issue delta specs, levelling is complicated<br> <TabAtkins> Rossen_: Lets move it to appendix for now, and if you experience any issues with issue tracking or maintenance, we can bring it back to approve for a l5<br> <TabAtkins> florian: So we'll have an appendix that means "dont' look at this too hard yet"?<br> <TabAtkins> TabAtkins: As opposed to a whole spec level that mans "don't look at this too hard yet"?<br> <fantasai> I agree with Florian that I don't think this is a good idea, it's confusing for both the editors and the readers.<br> <TabAtkins> florian: Okay, as long as it's marked well.<br> <fantasai> But I also don't want to spend more time on it<br> <TabAtkins> RESOLVED: Move the continue:fragments to an appendix, marking it as unstable.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8271#issuecomment-1412970187 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 February 2023 00:33:15 UTC