- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 29 Apr 2026 16:23:23 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-overscroll-1] Add an overscroll-behavior value which disables local boundary default actions`, and agreed to the following: * `RESOLVED: add a chain value to the overscroll-behavior property` * `RESOLVED: flackr is an editor for overscroll 1` * `ACTION: flackr to edit and prepare for publication` <details><summary>The full IRC log of that discussion</summary> <kbabbitt> flackr: currently when you are preventing overscroll you have a choice of whether to prevent local effects or completely stop any overscroll effect<br> <kbabbitt> ... for example elasticy effect on a local scroller<br> <kbabbitt> ... when vlad and I have been working through scrolling effects to implement things like swipe effects, it became apparent that having an elasticy effect on intermediate scrollers was undesirable<br> <kbabbitt> ... we think it would be useful to have a value that says scroll chains past local scroller but doesn't have a local effect<br> <kbabbitt> ... small modification we're proposing<br> <kbabbitt> ... completes the set of things you can do, can propagate scroll or not, can control whether a particular scroller has a boundary effect<br> <kbabbitt> astearns: this would not be the default behavior, something you would add for this set of circumstances?<br> <kbabbitt> flackr: correct<br> <kbabbitt> emilio: [missed]<br> <kbabbitt> ... auto chain allows chaining<br> <kbabbitt> flackr: and boundary effect<br> <kbabbitt> emilio: I guess that makes sense to me, if we were to design this property to [?]<br> <kbabbitt> ... even though this is not the default, this value reduces default be not allowing overscroll<br> <kbabbitt> ... support this proposal<br> <kbabbitt> flackr: ok<br> <davidjmarland> +1<br> <smfr> +1<br> <kbabbitt> astearns: proposal is to add a chain value to the overscroll-behavior property<br> <kbabbitt> ... concerns? objections?<br> <lwarlow> +1<br> <kbabbitt> RESOLVED: add a chain value to the overscroll-behavior property<br> <emilio> +1<br> <oriol> present-<br> <kbabbitt> fantasai: looks like the overscroll spoec hasn't been published since 2019, do we want to publish at this point?<br> <kbabbitt> astearns: this is a regular WD, right?<br> <kbabbitt> fantasai: yes<br> <kbabbitt> astearns: so editor's discretion to publish once this edit is in? or would you like a resolution?<br> <kbabbitt> fantasai: resolution for a reminder<br> <kbabbitt> astearns: objections to publishing a new draft of overscroll 1 when this edit is in?<br> <kbabbitt> ChrisL: if editors check through changes since last publication and update that would be nice<br> <kbabbitt> lwarlow: do we have current editors for this spec?<br> <kbabbitt> astearns: any volunteers?<br> <kbabbitt> flackr: Vlad?<br> <kbabbitt> astearns: will ping Vlad about it and see if he will sign up<br> <kbabbitt> flackr: I could be an editor I suppose<br> <kbabbitt> astearns: I nominate flackr for editor<br> <kbabbitt> fantasai: second<br> <kbabbitt> ChrisL: third<br> <kbabbitt> RESOLVED: flackr is an editor for overscroll 1<br> <kbabbitt> astearns: will let you take a look at state of draft before we publish<br> <fantasai> ACTION: flackr to edit and prepare for publication<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13370#issuecomment-4345564546 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 April 2026 16:23:24 UTC