Interactive elements within a positioned sticky element within an overflow scroll element on mobile after a scroll are not clickable
Reported by
stei...@gmail.com,
Mar 20 2018
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.162 Safari/537.36 Steps to reproduce the problem: 1. Open https://www.yr.no/nb/oversikt/time/1-72837/Norge/Oslo/Oslo/Oslo?i=1 in either mobile Chrome or, as I did, using devtools and device emulation set to iPhone 5 2. Scroll the dialog down a little 3. Try to click the close button to close the dialog What is the expected behavior? The dialog should close What went wrong? Nothing happens, the close button does not receive any click events. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 65.0.3325.162 Channel: stable OS Version: OS X 10.13.3 Flash Version: The bug *sometimes* disappears if you wait long enough after scrolling, but this is not consistent. If you scroll the dialog to its *top* the close button is clickable.
,
Mar 21 2018
,
Mar 21 2018
Thanks for filing the issue! Able to reproduce the issue on reported chrome version 65.0.3325.162 using Mac 10.13.1, Windows 10 and Ubuntu 14.04. As the issue is not seen in latest canary 67.0.3375.0 hence providing reverse bisect info. Reverse Bisect Information: ============================== Last Bad Build : 66.0.3334.0 First Good Build : 66.0.3335.0 You are probably looking for a change made after 532773 (known good), but no later than 532774 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/027952c6e83e11b51f16698ff49cdaa449374ffe..b74ffcfbbfc7b788d36aba2ee32850650fa2fe64 Suspecting: https://chromium.googlesource.com/chromium/src/+/b74ffcfbbfc7b788d36aba2ee32850650fa2fe64 Review URL: https://chromium-review.googlesource.com/885262 @Xianzhu Wang: Please help in reassigning it to others, if this is not related to your change. Note: Adding RB-stable as this seems to be a recent regression, Please remove if not applicable. Issue isn't seen in M60 and later builds, but it regressed in M65, hence adding label RegressedIn-65. Thanks!
,
Mar 21 2018
,
Mar 21 2018
Let's wait for the fix in M66.
,
Mar 21 2018
[Auto-generated comment by a script] We noticed that this issue is targeted for M-66; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-66 label, otherwise remove Merge-TBD label. Thanks.
,
Mar 21 2018
It's fixed in M66. No merge is needed. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by susan.boorgula@chromium.org
, Mar 20 2018