- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 04 Mar 2026 17:27:11 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-overscroll] overscroll-behavior should not prevent visual viewport "panning"`, and agreed to the following: * `RESOLVED: existing overscroll-behavior values that prevent scroll propagation don't prevent visual viewport panning` <details><summary>The full IRC log of that discussion</summary> <emilio> vmpstr: if you have a scroller with `overscroll-behavior: contain` and you pinch-zoom<br> <emilio> ... then you can't pan that visual viewport around if your mouse is in there<br> <emilio> q+<br> <emilio> ... I understand why<br> <emilio> ... but I find it unexpected<br> <emilio> ... the panning part seems like a very strange and unexpected limitation<br> <flackr> +1<br> <emilio> ... I'd like to change that<br> <fantasai> scribe+<br> <Rossen> ack emilio<br> <fantasai> emilio: Are people using it to implement their own panning behavior?<br> <fantasai> emilio: e.g. Google Maps, when you pinch-zoom, the app needs to do something, handle its own gestures<br> <fantasai> emilio: I could imagine them using this instead of event listeners and defaulting<br> <fantasai> flackr: If an app is implementing pinch-zoom, they shouldn't allow pinch-zoom into visual viewport<br> <fantasai> emilio: What if it's embedded? You only want to constrain pinch-zoom in that area.<br> <emilio> vmpstr: from my perspective, if there are valid use cases for that we should enable them. But I think the default behavior shouldn't be there<br> <fantasai> vmpstr: If valid use cases for that, we should enable them, but default behavior of "I don't want to change my scroll, side-effect is that you can't pan around pinch-zoomed area" is not great<br> <fantasai> emilio: I agree with that in theory, but a bit worried about ppl abusing that already, but we can try<br> <fantasai> emilio: There's a good use case to prevent pinch-zooming in a particular scroller. Embedded map use case, for example. Seems pretty reasonable to specify that with CSS, so that you [missed] and deal with pinch-zoom yourself.<br> <fantasai> emilio: But we could introduce a new syntax for that.<br> <fantasai> emilio: Just worried about other pages relying on it.<br> <fantasai> flackr: There's a touch-action property that you can use to prevent pinch-zooming.<br> <fantasai> flackr: Don't think we have equivalent for mouse zoom.<br> <fantasai> flackr: Invoking browser zoom is going to be a weird situation.<br> <fantasai> flackr: In any case overscroll-behavior is not how you would avoid pinch-zoom panning.<br> <fantasai> vmpstr: I pinch-zoom a lot, it's very disturbing when I can't pan around that<br> <smfr> q+<br> <fantasai> vmpstr: If the site has some intentional desire here, they should indicate explicitly using a special property or something.<br> <Rossen> ack smfr<br> <emilio> scribe+<br> <emilio> smfr: I support the proposal, I think gmaps shows a message (hold the command key or so) to zoom the map<br> <emilio> PROPOSED: existing overscroll-behavior values that prevent scroll propagation don't prevent visual viewport panning<br> <flackr> +1<br> <emilio> RESOLVED: existing overscroll-behavior values that prevent scroll propagation don't prevent visual viewport panning<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12919#issuecomment-3999024623 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 4 March 2026 17:27:12 UTC