Contact emails: ara...@microsoft.com
CSSWG discussion: [css-overscroll] Whether to move position:fixed elements during overscrolling · Issue #6299 · w3c/csswg-drafts (github.com)
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
Chromestatus: Prevent overscroll for fixed elements. - Chrome Platform Status (chromestatus.com)
Risks:
Debuggability: N/A
Is this feature fully tested by web-platform-tests?
Yes. We did a
dry run
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
Estimated milestone:
105
Tracking bugs:
Misc:
Contact emails: ara...@microsoft.com
CSSWG discussion: [css-overscroll] Whether to move position:fixed elements during overscrolling · Issue #6299 · w3c/csswg-drafts (github.com)
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
Chromestatus: Prevent overscroll for fixed elements. - Chrome Platform Status (chromestatus.com)
Risks:
- Interoperability: Firefox/Safari still moves fixed elements on overscroll.
--
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.
ExplainerAre 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.
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.
--
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/5f816069-432f-b85a-4abc-ada3ea0dc71f%40mozilla.com.
Ah yes! That counts, and saves filing a signal. Thanks Emilio!On Fri, May 27, 2022 at 1:46 PM Emilio Cobos Álvarez <emi...@mozilla.com> wrote:On 5/27/22 20:40, Chris Harrelson wrote:
> No. it has to be done via the https://bit.ly/blink-signals
> <https://bit.ly/blink-signals> process, because otherwise we might
> accidentally misconstrue their true organizational positions.
FWIW in case it saves some time, we're actively working on this in
<https://bugzilla.mozilla.org/show_bug.cgi?id=1760368>.
-- Emilio
--
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+unsubscribe@chromium.org.
Thanks for the explainer. My question regarding a spec still stands :)
On Friday, May 27, 2022 at 10:49:31 PM UTC+2 Chris Harrelson wrote:
Ah yes! That counts, and saves filing a signal. Thanks Emilio!On Fri, May 27, 2022 at 1:46 PM Emilio Cobos Álvarez <emi...@mozilla.com> wrote:On 5/27/22 20:40, Chris Harrelson wrote:
> No. it has to be done via the https://bit.ly/blink-signals
> <https://bit.ly/blink-signals> process, because otherwise we might
> accidentally misconstrue their true organizational positions.
FWIW in case it saves some time, we're actively working on this in
<https://bugzilla.mozilla.org/show_bug.cgi?id=1760368>.
-- Emilio
--
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/5f816069-432f-b85a-4abc-ada3ea0dc71f%40mozilla.com.
--
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/4191983d-d0fd-4dce-beed-d12ee7115a46n%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9OX%3D3dPBwC3ARwiL6GMSx%3DASY5EiEMOPC5e4S0iJUcWA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5efc25ed-0c43-4c7d-e877-d05b6a0512f3%40chromium.org.
The failing tests have now been fixed. Thanks for the quick review Chris !
Now that this is done, can you please tell me what the process would look like to get this ON in stable? I have a CL for this but I assume you’d want to run experiments first?
Thanks,
Rahul
You have the approval needed for shipping on stable, i.e. land that patch. It will get some testing by going through Canary and Beta releases, but if you feel some uncertainty you can also add the plumbing that would let it be turned off remotely (flags, finch). You will need some assistance by Google employees for that though.
/Daniel
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/SJ0PR00MB1141ACDFA8EA11EAF30D96B3A6A29%40SJ0PR00MB1141.namprd00.prod.outlook.com.
Thanks Daniel, the CL has landed !
Also, I had added a base::Feature flag a couple of weeks ago. I’m assuming that should make it controllable remotely. If not, please let me know.
PS: Thank you all for your reviews on this feature. We appreciate it… 😊
I will keep an eye out for any issues that pop up in the coming days.
Thanks,
Rahul
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/1985d9a0-04e9-f1f3-75d4-c398b28455dd%40gmail.com.