[css-overflow-3][css-overflow-4][css-overflow-5] Reshuffling Levels

[fantasai]

Since @frivoal and I are trying to stabilize CSS Overflow L3 for CR, we'd like to propose the following shuffle of features:

• Shift line-clamp and its longhands from L3 to L4.
• Push any extensions to overflow-* properties not yet implemented by two browsers to L4.
• Shift all the experimental overflow fragments stuff and the scrollbar-gutter extensions appendix from L4 to a new L5 spec.

We're open to suggestions on what to do with the text-overflow extensions in L4, whether to keep it there or shift it to L5. It's pretty rough atm, but if anyone is interested we can try to polish it up. https://drafts.csswg.org/css-overflow-4/#text-overflow

[astearns]

Could we resolve on this async? The L3->L4 moves seem good to me, and I would be fine leaving the L4-L5 split up to editor’s discretion.

[fantasai]

@astearns I'd be interested in getting implementer input on the L4 text-overflow question.

[astearns]

Switching back to Agenda+, unless we get implementer opinions expressed here before we get to it on a call.

[css-meeting-bot]

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.

The full IRC log of that discussion

<TabAtkins> fantasai: florian and i wanted to prepare Overflow 3 for CR
<TabAtkins> fantasai: We'd like to shift the line-clamp stuff to L4
<TabAtkins> fantasai: Also anything else that's not already in 2 browses
<TabAtkins> fantasai: And then shift the overflow-fragments stuff from L4 to L5
<TabAtkins> fantasai: Also, there's some extensions to text-overflow in L4 - do we want to keep it there or push them to L5?
<TabAtkins> fantasai: q to the WG
<fantasai> -> https://drafts.csswg.org/css-overflow-4/#text-overflow
<TabAtkins> florian: I'd just move the "keep" fragment stuff to L5
<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
<TabAtkins> florian: So move "continue: fragments" to L5, move line-clamp to L4, keep the rest as-is
<TabAtkins> Rossen_: The L3 to L4 makes sense to me
<TabAtkins> Rossen_: Not sure what moving to L5 buys us for now.
<TabAtkins> Rossen_: ARe we expecting L4 to advance fast?
<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
<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.
<TabAtkins> fantasai: and continue:fragments is very experimental and complicate
<fantasai> TabAtkins: I'd rather push to an appendix
<TabAtkins> florian: that works too
<TabAtkins> florian: It's less helpful for issue triage, github labelling
<TabAtkins> florian: But in terms of spec, whichever
<TabAtkins> fantasai: continue:fragments is on the level of CSS Regions in terms of CSS layout.
<TabAtkins> fantasai: Just don't think it's not a great idea
<TabAtkins> Rossen_: Think we should do the resolutions separately
<TabAtkins> Rossen_: So objections to moving line-clamp to L4?
<TabAtkins> [no objections
<TabAtkins> RESOLVED: Move line-clamp stuff from Overflow 3 to 4
<TabAtkins> florian: Having done that, I'm opposed to keeping continue:fragments in the main body
<TabAtkins> florian: I have a pref for l5 for triage purposes
<fantasai> TabAtkins: I don't like having single-issue delta specs, levelling is complicated
<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
<TabAtkins> florian: So we'll have an appendix that means "dont' look at this too hard yet"?
<TabAtkins> TabAtkins: As opposed to a whole spec level that mans "don't look at this too hard yet"?
<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.
<TabAtkins> florian: Okay, as long as it's marked well.
<fantasai> But I also don't want to spend more time on it
<TabAtkins> RESOLVED: Move the continue:fragments to an appendix, marking it as unstable.