W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2021

Re: [csswg-drafts] [css-overflow] proposal: scroll-index (priority) (#5670)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Tue, 27 Jul 2021 16:17:32 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-887648981-1627402651-sysbot+gh@w3.org>
The CSS Working Group just discussed `scroll-index`.

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> topic: scroll-index<br>
&lt;emilio> github: https://github.com/w3c/csswg-drafts/issues/5670<br>
&lt;emilio> florian: not my issue but I wanted to give it some attention<br>
&lt;TabAtkins> q+<br>
&lt;emilio> ... The use case is something we see on lots of websites, with a top banner that disappears but reappears if you scroll up again<br>
&lt;emilio> ... This author is thinking of this in terms of nested scrollers<br>
&lt;emilio> ... where your top banner is in a scroller outside the inner one<br>
&lt;emilio> ... we always prioritize the inner scroller<br>
&lt;flackr> q+<br>
&lt;emilio> ... but the author was proposing to prioritize the outer scroller, and only when that is exhausted scroll the inner one<br>
&lt;emilio> ... no strong opinion, there could be some parallels with overscroll-behavior<br>
&lt;emilio> ... just wanted to bring some attention to the issue<br>
&lt;emilio> TabAtkins: I find the use case good to address because lots of sites do this badly<br>
&lt;emilio> ... but I think this approach is not the way to go<br>
&lt;Rossen_> ack TabAtkins<br>
&lt;emilio> ... first this doesn't do what lots of sites do which is having a minified banner<br>
&lt;emilio> ... second, it seems very easy to screw up a page if you only test on desktop<br>
&lt;emilio> ... the current behavior is safer for that<br>
&lt;emilio> ... So I think the problem is good, the solution is bad<br>
&lt;emilio> ... we probably want another way to do this<br>
&lt;Rossen_> ack flackr<br>
&lt;emilio> flackr: I was going to point pretty much the same<br>
&lt;emilio> ... you only want to do this scroll priority inversion for the topmost scroller<br>
&lt;emilio> ... if you have nested ones then scrolling the header is probably not what the user intended<br>
&lt;Rossen_> q?<br>
&lt;emilio> ... so it seems a bit of a problematic solution<br>
&lt;emilio> Rossen_: sounds like the use case is well recognized, but the proposed solution is not<br>
&lt;argyle> agree with robert and tab<br>
&lt;emilio> ... I suggest to go back to the issue to discuss the solution<br>
&lt;emilio> florian: so the issue was proposing the solution, you're proposing to repurpose it right?<br>
&lt;emilio> Rossen_: sure<br>
&lt;emilio> florian: sounds good<br>
&lt;emilio> Rossen_: yeah, it seems like we should explore a good solution for this problem<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5670#issuecomment-887648981 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 27 July 2021 16:17:34 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:39 UTC