- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Jun 2023 16:34:53 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-backgrounds-4] Split CSS Backgrounds into separate specs?`, and agreed to the following: * `RESOLVED: Adopt proposal above, background-* into css-backgrounds, border-* and box-shadow into css-borders, and box-decoration-break into css-box` <details><summary>The full IRC log of that discussion</summary> <fantasai> scribenick: fantasai<br> <fantasai> SebastianZ: Suggestion is to split up the CSS Background 4 spec into 3<br> <fantasai> SebastianZ: initial suggestion was to split into 2, but this didn't turn out very well<br> <fantasai> SebastianZ: idea is to focus each spec on one thing<br> <fantasai> SebastianZ: because backgrounds covers backgrounds, borders, and box shadow<br> <fantasai> SebastianZ: and we want to edit separately, and also make progress separately<br> <fantasai> SebastianZ: suggestion is into css-background-4 related to backgrounds<br> <fantasai> SebastianZ: Borders 4 cover everything border-related<br> <fantasai> SebastianZ: and CSS box-decorations-4 which covers box shadow and its longhands and anything else related to box decorations<br> <Rossen_> ack fantasai<br> <fantasai> https://www.w3.org/TR/css-box-3/<br> <drott> fantasai: we also have a spec called box-model<br> <drott> fantasai: spec that covers margins and paddings<br> <drott> fantasai: that would put us into quite a lot of spec<br> <drott> fantasai: backgrounds is fairly self evident, other splits are less evident<br> <drott> fantasai: divisions not super clean, border-... applies kinda a background<br> <drott> fantasai: might make it hard for people to look for - if we have it spread across 4 specs<br> <drott> SebastianZ: bringing in the box model, which wasn't covered in that issue<br> <drott> SebastianZ: idea was to have clear concepts borders, backgrounds, decorations<br> <drott> fantasai: border-image has a background to it - concerned as to: What's what?<br> <drott> fantasai: i like the idea of splitting it, but uncertain about how to do it cleanly, making it so it's obvious<br> <drott> SebastianZ: counter proposal? atm it's confusion: CSS Backgrounds and Borders, box shadow not mentioned in the title, mixing things<br> <fantasai> e.g. box-decoration-break affects borders and background also<br> <drott> fantasai: don't have a good answer atm<br> <drott> rossen_: evident we have shifted in how borders and backgrounds are becoming more decorative<br> <drott> rossen_: over time, all of these concepts have progressed - seems reasonable for backgrounds, borders, decorations to be split<br> <drott> rossen_: to fantasai's point, we have some horizontal concepts in .. box model?<br> <drott> fantasai: they're interconnected: use case: author: where do i find the corresponding spec?<br> <drott> fantasai: question is: where do people find things<br> <drott> fantasai: box-model spec suitable place for box decorations?<br> <drott> SebastianZ: many new features coming to background and borders - if put in box-spec spec becomes very long<br> <drott> fantasai: backgrounds and borders being separate is ok, box decoration being a separate spec seems too much<br> <drott> rossen_: if we split this into only two specs, as a starting point<br> <drott> rossen_: let's say borders and backgrounds would be split off<br> <drott> rossen_: Where to put decorations?<br> <castastrophe> q+<br> <fantasai> fantasai: I think putting box-shadow into borders makes sense, it outlines the border<br> <fantasai> fantasai: but box-decoration-break could maybe go into css-box<br> <Rossen_> ack castastrophe<br> <fantasai> fantasai: since it also affects margins / padding<br> <drott> castastrophe: what would be the downside of a long spec?<br> <drott> castastrophe: we could also do cross-linking, and use it to a sub-specification?<br> <Rossen_> ack fantasai<br> <drott> jensimmons: sounds like there might not be enough consensus to resolve?<br> <drott> fantasai: split into backgrounds 4 and borders 4<br> <fantasai> fantasai: backgrounds-* into css-backgrounds, borders-* into css-borders<br> <fantasai> fantasai: box-shadow into css-borders<br> <fantasai> fantasai: box-decoration-break into css-box<br> <drott> SebastianZ: If that seems reasonable to you - perhaps we could go ahead with that proposal? Wanna address castatstrophe point?<br> <fantasai> s/SebastianZ/Rossen/<br> <drott> SebastianZ: it's box-shadow that does not fit well into one of those specs<br> <drott> SebastianZ: discussion started with others raising that box-shadow should stand on its own<br> <drott> fantasai: box-shadow should go into the border spec<br> <fantasai> fantasai: it's effectively functioning as a border<br> <fantasai> fantasai: box-decoration-break would go into css-box; it affects margins and padding too<br> <drott> rossen: would the proposed split into borders 4 and backgrounds 4, with fantasai's described split suitable?<br> <fantasai> plinss: I'm in favor of fantasai's proposal, but feel like shadows should go into backgrounds<br> <fantasai> plinss: but I don't feel strongly<br> <fantasai> plinss: it doesn't affect sizing<br> <fantasai> fantasai: neither does border-image<br> <fantasai> Rossen_: [summarizes proposal]<br> <fantasai> background-* into css-backgrounds<br> <ntim> sounds good to me<br> <fantasai> border-* (including border-image) into css-borders<br> <fantasai> box-shadow into css-borders<br> <fantasai> box-decoration-break into css-box<br> <fantasai> Rossen_: any objections?<br> <fantasai> RESOLVED: Adopt proposal above, background-* into css-backgrounds, border-* and box-shadow into css-borders, and box-decoration-break into css-box<br> <fantasai> SebastianZ: thanks for resolving<br> <fantasai> Rossen_: it's important to get to topics that are not everyone's most important, not let them languish<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7664#issuecomment-1611748037 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 June 2023 16:34:55 UTC