- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jan 2025 00:05:06 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-scrollbars] What is "the background"`. <details><summary>The full IRC log of that discussion</summary> <TabAtkins> florian: a while back we talked aobut using transparent colors when setting scrollbar colors<br> <TabAtkins> florian: we resovled that if you set the transparent thumb, you see the track. if you set transparent track, you see the backgroudn of the element<br> <TabAtkins> florian: we didn't define waht actually is meant by "background"<br> <TabAtkins> florian: testing, we didn't mean "background", we seemed to mean "element".<br> <ChrisL> q+<br> <TabAtkins> florian: almost agreement in brwosers<br> <TabAtkins> florian: nuance, content of the element isn't seen, but that's just because it's clipped to the padding area so it's not there to *be* seen<br> <TabAtkins> florian: that's controlled by overflow-clip-margin, default is padding-box<br> <emilio> q+<br> <TabAtkins> florian: thus far I think Chrome and Firefox completely agree<br> <TabAtkins> florian: only one tiny difference, think it's a bug<br> <TabAtkins> florian: if you do background-attachment local, in Chrome the bg is clipped to the padding box.<br> <TabAtkins> florian: dont' think there's any spec justification for that<br> <TabAtkins> florian: wasn't meaningfully observable before, but in Chrome you can't see a local bg because it's clipped; in firefox you see the bg<br> <astearns> ack ChrisL<br> <TabAtkins> florian: just need to figure out how to define that stacking/painting<br> <TabAtkins> ChrisL: what we want is a term for "entire rendered content of the element"<br> <TabAtkins> florian: Might be a term for that already, just don't know it<br> <TabAtkins> q+<br> <astearns> ack emilio<br> <TabAtkins> emilio: I don't think... overflow-clip-margin doesn't apply to scrollable boxes generally<br> <TabAtkins> emilio: but the rest i think is correct, and we should agree on this behavior<br> <astearns> ack TabAtkins<br> <emilio> TabAtkins: I think all that's necessary is defining when scrollbars are painted in the CSS stacking model<br> <emilio> florian: so we'd monkey-patch that algorithm from the scrollbars spec?<br> <emilio> TabAtkins: no, that's on another spec but yeah<br> <emilio> q+<br> <astearns> ack emilio<br> <TabAtkins> emilio: I agree, but the specifics of where they're painted is maybe a bit weird...<br> <TabAtkins> emilio: need to dig into it<br> <TabAtkins> emilio: might be some cases where we'd intentionall put scrollbars over content they aren't usually over<br> <TabAtkins> emilio: will need to check<br> <TabAtkins> emilio: but i agree we need to define the right stacking order of scrollbars<br> <TabAtkins> astearns: so florian, you ahve a way forward<br> <TabAtkins> florian: yes, details TBD, but can agree that behind a transparent scrollbar you'll see the entire underlying content<br> <TabAtkins> florian: not just showing you one specific layer of the element<br> <emilio> q+<br> <astearns> ack emilio<br> <TabAtkins> astearns: proposed: specify that transparent scrollbars show thru whatever's underneath them<br> <TabAtkins> emilio: checking, i think gecko puts classic and overlay scrollbars at a different stacking position<br> <TabAtkins> emilio: wrt element contents at least<br> <TabAtkins> astearns: so back to issue now<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10524#issuecomment-2623209316 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 January 2025 00:05:07 UTC