- From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Mar 2022 17:20:47 +0000
- To: public-css-archive@w3.org
Re JS APIs: currently, Gecko and Chromium's implementations of overscroll do not affect any developer APIS, and are purely a "UA affordance" in that sense. Overscroll implementations differ between platforms (e.g. I know of at least 3 approaches: rubber-band/translate [iOS/Mac], stretch [Android current], glow [old Android]), and it's good to allow UAs to try out different affordances. Pull-to-refresh was a use case @smfr mentioned as being helped by the current negative scroll offfset approach in Safari. Therefore, I propose: * Specify that overscroll does not affect any JS APIs * Solve pull-to-refresh (which I agree is worth solving) with other APIs that will be independent of the approach to overscroll, and work on platforms without overscroll affordances -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6299#issuecomment-1076593853 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 March 2022 17:20:48 UTC