On Fri, May 27, 2022 at 11:38 AM 'Ben Mathwig' via blink-dev < blink-dev@chromium.org> wrote:
> Explainer > <https://docs.google.com/document/d/10vNhX_UWT0RJ8v1NfIrX385t1fxIbhY-1IbPc-a_xwo/edit?usp=sharing> > > Are the links to open bugs on Mozilla and WebKit an indication of > position? It looks like comments on these threads point towards a positive > position. > No. it has to be done via the https://bit.ly/blink-signals process, because otherwise we might accidentally misconstrue their true organizational positions. > > --Ben > > On Tuesday, May 24, 2022 at 11:44:16 PM UTC-7 yoav...@chromium.org wrote: > >> Hey Rahul! >> >> A few things missing with the intent: >> >> - An explainer would be helpful to clarify the motivation for this >> and if this has any web exposed impact (and e.g. how would developers that >> want to keep to current behavior could cope with different engines doing >> different things) >> - Is this specified? I see the WG discussion, but not sure if a spec >> change followed >> - Can you ask for official Mozilla and WebKit positions? ( >> https://bit.ly/blink-signals) >> >> Cheers :) >> Yoav >> >> On Tue, May 24, 2022 at 8:08 PM Robert Flack <fla...@chromium.org> wrote: >> >>> >>> >>> On Tue, May 24, 2022 at 1:27 PM 'Rahul Arakeri' via input-dev < >>> inpu...@chromium.org> wrote: >>> >>>> *Contact emails*: ara...@microsoft.com >>>> >>>> >>>> >>>> *CSSWG discussion*: [css-overscroll] Whether to move position:fixed >>>> elements during overscrolling · Issue #6299 · w3c/csswg-drafts (github.com) >>>> <https://github.com/w3c/csswg-drafts/issues/6299> >>>> >>>> >>>> >>>> *Summary*: Currently, position:fixed elements move when the scroller >>>> is overscrolled. With this change, we intend to prevent fixed elements from >>>> moving during an elastic overscroll. >>>> >>>> >>>> >>>> *Blink component*: Blink>Scroll >>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component%3ABlink%3EScroll> >>>> >>>> >>>> >>>> >>>> *Chromestatus*: Prevent overscroll for fixed elements. - Chrome >>>> Platform Status (chromestatus.com) >>>> <https://chromestatus.com/feature/5381155556687872> >>>> >>>> >>>> >>>> *Risks*: >>>> >>>> - Interoperability: Firefox/Safari still moves fixed elements on >>>> overscroll. >>>> >>>> Just wanted to clarify, iOS Safari does not move fixed position >>> elements on overscroll except when you start scrolling at the scroller edge >>> in order to make room for the refresh affordance, so there's already some >>> inconsistency here. >>> >>> Also it is considered a bug that fixed content does still move on >>> Safari desktop >>> <https://github.com/w3c/csswg-drafts/issues/6299#issuecomment-1036996792> so >>> they would likely be willing to follow along with this change. >>> >>> >>>> >>>> - Interacting with websites will *feel* different (going forward) >>>> on platforms that support overscroll. This may lead to some web devs >>>> amending pages to preserve their original UX. We are currently running >>>> experiments in Microsoft Edge to determine user impact and would also >>>> discuss the possibility of doing origin trials in Chromium with Google >>>> engineers. >>>> >>>> >>>> >>>> *Debuggability*: N/A >>>> >>>> *Is this feature fully tested by web-platform-tests?* >>>> >>>> Yes. We did a dry run >>>> <https://chromium-review.googlesource.com/c/chromium/src/+/3651546> >>>> with the feature turned on and noticed test failures. They will need to be >>>> addressed before the feature can be turned on. >>>> >>>> *Flag name*: FixedElementsDontOverscroll >>>> >>>> - Usage: chrome.exe --enable-features=ElasticOverscroll >>>> --enable-blink-features=FixedElementsDontOverscroll >>>> >>>> >>>> >>>> *Estimated milestone*: >>>> >>>> 105 >>>> >>>> >>>> >>>> *Tracking bugs*: >>>> >>>> - Chromium: >>>> - 585766 - Overscroll shouldn't affect fixed elements - chromium >>>> <https://bugs.chromium.org/p/chromium/issues/detail?id=585766> >>>> - Firefox: >>>> - *https://github.com/mozilla/wg-decisions/issues/757 >>>> <https://github.com/mozilla/wg-decisions/issues/757>* >>>> - *https://bugzilla.mozilla.org/show_bug.cgi?id=1760368 >>>> <https://bugzilla.mozilla.org/show_bug.cgi?id=1760368>* >>>> - Webkit: >>>> - *https://bugs.webkit.org/show_bug.cgi?id=206227 >>>> <https://bugs.webkit.org/show_bug.cgi?id=206227>* >>>> >>>> >>>> >>>> *Misc:* >>>> >>>> - BlinkOn 16 talk: (1311) Keynote Presentation & Lightning Talks - >>>> Session 1 [BlinkOn 16] - YouTube >>>> <https://www.youtube.com/watch?v=o1pJJuQiCmQ&t=1378s> >>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "blink-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to blink-dev+...@chromium.org. >>> To view this discussion on the web visit >>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJh39TOdn6Hksb1Zb8H5oqsUu0xvS%2BmqvypEghDsNtsQRFr1Nw%40mail.gmail.com >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJh39TOdn6Hksb1Zb8H5oqsUu0xvS%2BmqvypEghDsNtsQRFr1Nw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5f89f3bd-399d-44b5-a8de-747181df317cn%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5f89f3bd-399d-44b5-a8de-747181df317cn%40chromium.org?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9py0gt_uVQL8T7k3n_zBFhrmxFd3gx%3Djq-JYFery84Qg%40mail.gmail.com.
