Issue metadata
Sign in to add a comment
|
Regression: Unable to scroll page after exisiting browser from fullscreen mode.
Reported by
db...@etouch.net,
Jun 6 2018
|
||||||||||||||||||||
Issue descriptionChrome Version: 67.0.3396.79 Revision 161bdad7314804dc8c72f850396fcd696e8863e8-refs/branch-heads/3396@{#755}(64 bit) OS: Mac(10.12.6,10.13.1,10.13.6) What steps will reproduce the problem? (1) Launch chrome,navigate to https://permission.site and click on 'Fullscreen'. (2) Now click on exist fullscreen button of browser to exist fullscreen. (3) Try to scroll page and observe. Actual: Unable to scroll page after exisiting browser from fullscreen. Expected: Should be able to scroll page after exisiting browser from fullscreen. This is a regression issue, broken in 'M66', below is bisect info: Good Build:66.0.3450.0 Bad Build: 66.0.3451.0 You are probably looking for a change made after 537239 (known good), but no later than 537240 (first known bad). CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+log/d3f8d267ec975458cd5adfb951f38bb5c019ad24..25ceb614d45226635207d6125c4f339c3e34492c Suspect: https://chromium.googlesource.com/chromium/src/+/25ceb614d45226635207d6125c4f339c3e34492c @ccameron: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Note: 1.Issue is also seen on M67 Beta build #67.0.3396.62,. M68 Dev build #68.0.3440.15 and M69 Canary build #69.0.3451.0. 2.Issue is not seen on Windows(7,8,8.1,10) and Linux(14.04) OS.
,
Jun 6 2018
->bokan to weigh in on correct input behavior (and b/c this is similar to issue 704070). I think that this is the correct behavior - this seems unrelated to the bisected change - the behavior (no scrolling in fullscreen) matches Firefox and Safari - the post at [1] suggests that document.body.requestFullscreen won't allow scrolling [1] https://stackoverflow.com/questions/45031687/scrolling-disabled-in-the-webpage-when-full-screen-mode-is-triggered
,
Jun 6 2018
(actually sending to bokan@)
,
Jun 7 2018
Re#2: Sounds to me like the reported issue is that the page is unscrollable after *exiting* fullscreen. That said, I can't reproduce this locally, either on Stable (67.0.3396.62) or Canary (69.0.3451.0). dbote@, is there anything else about your setup that may be unique (desktop or laptop? retina or non-retina screen? Scrolling with mouse wheel or trackpad?)? Can you try it on another machine? If it's still reproducing, please capture and attach a trace here using instructions here: https://www.chromium.org/developers/how-tos/submitting-a-performance-bug. Another question: Can you scroll by dragging scrollbars or using keyboard?
,
Jun 15 2018
Ping, dbote@ - does this still repro? Can you please provide the requested information in #4?
,
Jun 18 2018
With respect comment 4: Issue is still reproducible on latest canary build #69.0.3464.0, here attached the trace for the same. Unable to scroll page by using keyboard or dragging scrollbars. Please find attached screen cast for the same. Thank you.
,
Jun 18 2018
Hmm, still can't repro. dbote@, are you using an external mouse with a wheel or the mac touchpad? Trace shows all scroll events being delivered correctly. Can you try in incognito mode and all flags reset in chrome://flags?
,
Jun 19 2018
With respect to comment #7 Rechecked this issue on Mac(10.12.6,10.13.1,10.13.6) OS using latest Canary # 69.0.3464.0 and able to reproduce this issue using "external mouse with a wheel" and "mac touch pad" both. This issue is also reproducible on Incognito mode with all flags reset in chrome://flags. please kindly refer attached screen cast for reference. Thank You.
,
Jul 9
I took a closer look at the trace (I was never able to repro myself). It looks like we're processing the gesture scrolls correctly but they're not causing an offset change so we don't generate any new frames. We can't tell from the trace but my best guess the reason is that we don't change the UserInputScrollable bit on the scrollable area after exiting fullscreen. Chris, I'm not quite sure what your patch does but it seems related to resizes. IIRC, the fullscreen state was propagated to Blink via a resize so it seems plausible it could be related. Could you take another look (I'm OOO for the next 3 weeks) or retriage.
,
Aug 17
ccameron@: ping I'm able to repro this now on a different Mac: MacBook Pro 2015 (13in Retina) on OSX 10.11.6 (El Capitan). Switching tabs and coming back makes the page scrollable again. Also of note: exiting fullscreen with the escape key works correctly. Only using the green button in the top left corner shows the issue.
,
Sep 14
Going back to #1, this behavior reproduces on Safari and Firefox, so it's not clear to me what is correct behavior. Also, we've switch from using Cocoa to using MacViews, so our fullscreen behavior is likely different now from when the bug was filed. Marking as available.
,
Sep 14
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ccameron@chromium.org
, Jun 6 2018