- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Apr 2025 15:58:33 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-overflow-5] Enforce layout containment on ::scroll-marker-group`, and agreed to the following: * `RESOLVED: ::scroll-marker-group gainst "contain: layout !important" in the UA style sheet` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> flackr: we're proposing to enforce layout containment on scorll-marker-group. it avoids a lot of complex situations<br> <TabAtkins> flackr: like having intruding flaots, or abspos on a scroll marker resulting in it not being in the group<br> <TabAtkins> flackr: doesn't seem like there's a strong use-case to *not* have layout containment<br> <TabAtkins> flackr: and just less surprising in general to have it<br> <fantasai> TabAtkins: we already partially relaxed the size containment, right?<br> <TabAtkins> flackr: yup<br> <TabAtkins> astearns: only reason to not do it that i can think of is it's just yet anohter thing that changes the value of properties wihtout being explicitly set<br> <TabAtkins> astearns: sometimes hard to teach<br> <TabAtkins> flackr: i think we can set this in the UA style for ::scroll-marker-group<br> <TabAtkins> fantasai: would that be !important<br> <TabAtkins> flackr: yes<br> <TabAtkins> TabAtkins: and would then show up in devtools<br> <TabAtkins> astearns: so proposal is we set size containment for scorll-marker-groups as !important in the UA sheet<br> <TabAtkins> RESOLVED: ::scroll-marker-group gainst "contain: layout !important" in the UA style sheet<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11708#issuecomment-2773048882 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 April 2025 15:58:34 UTC