Issue metadata
Sign in to add a comment
|
Regression: PDF becomes unresponsive after exiting from full-screen.
Reported by
aiman.an...@etouch.net,
Apr 13 2018
|
||||||||||||||||||||||
Issue descriptionChrome Version: 67.0.3396.0 (Official Build)Revision 9ef2aa869bc7bc0c089e255d698cca6e47d6b038-refs/heads/master@{#550428} (32/64 Bit) OS: Win(7,8,8.1,10). Pre-Condition : Download the extension from the given link (https://chrome.google.com/webstore/detail/pdf-viewer/oemmndcbldboiebfnladdacbdfmadadm?hl=en) Test URL: http://www.stepupnihongo.com/images/SUN3_L-51.pdf What steps will reproduce the problem? 1. Launch chrome, navigate to above test url. 2. Click on 'Full-screen Icon' in toolbar and press 'ESC' key. 3. Repeat step (2) 5-6 times and observe. Actual Result: PDF becomes unresponsive after exiting from full-screen.. Expected Result: PDF should not be unresponsive. This is a regression issue, broken in M-67 series, (Unable to provide bisect using per-revision script hence providing suspect using old bisect script) Good Build:67.0.3395.0 Bad Build:67.0.3396.0 Narrow Bisect https://chromium.googlesource.com/chromium/src/+log/5fbb75e93162093522879e707a13295b7452ef06..b27727abc409de34bbd452c03fe0916551b813de Suspecing: r550356? yuweih@: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: Issue is not reproducible on Mac(10.12.6, 10.13.1, 10.13.5) and Linux(14.04 LTS) OS. Thank You!
,
Apr 13 2018
,
Apr 20 2018
@govind: Could you help me find QA resource to repro or bisect this issue per revision? I couldn't repro this issue on my personal Windows PC and I don't have a Windows PC setup for Chromium development either..
,
Apr 20 2018
aiman.ansari@, could you ptal comment #1.
,
Apr 20 2018
,
Apr 20 2018
,
Apr 20 2018
The PDF Viewer in question is not the Chrome PDF Viewer.
,
Apr 20 2018
Yeah,sorry. Thank you.
,
Apr 23 2018
Applying "RBS" for M-67 for tracking purpose.
,
Apr 23 2018
w.r.t to comment #1, yuweih@chromium.org: To answer your question, I was able to see the 'Exit button' after enabling the flag chrome://flags/#enable-experimental-fullscreen-exit-ui after hovering mouse on top of the screen. Now, w.r.t bug, I checked the issue on latest Canary #68.0.3403 'with and without flag' and was not able to reproduce the issue on the same. I am able to reproduce the issue on reported version build #67.0.3396.0 and it is fixed in build #68.0.3397.0. Hence providing the reverse bisect details, Please find the change-log below: https://chromium.googlesource.com/chromium/src/+log/a98c719c8388a1bc07357b3113242c70e97fde5b..fdada01a75db65126449561b8b7b62adb902efe8?pretty=fuller&n=10000 Got the above change-log url, but unable to find the correct suspect. @yuweih: Could you help me in reassigning the bug. Thank You!
,
Apr 23 2018
Sounds like it is not related to the fullscreen exit UI. I looked at the change-log but couldn't find any commit that seems to fix the issue either... Are you able to repro this issue on 3396 dev channel (i.e. 67.0.3396.12)?
,
Apr 24 2018
Hi, Retested the above issue on Dev build #67.0.3396.12 using Windows(7,8,8.1,10) OS and unable to reproduce the issue here. Thank You!
,
Apr 24 2018
Update: Retested the above issue on market Dev build #67.0.3396.10 and today's release Dev build #67.0.3396.18 using Windows(7,8,8.1,10) OS and unable to reproduce the issue here. Thank You!
,
Apr 24 2018
Seems like there was something weird with the 67.0.3396.0 build... Given that it is no longer reproducible on the 3396 branch, shall I close this bug?
,
Apr 25 2018
M67 Stable promotion is coming soon. Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge into the release branch ASAP. Thank you.
,
Apr 25 2018
Looks like the reporter can no longer repro the issue on latest M67 build. Let's close it for now. Feel free to reopen this bug if you see this problem happening again. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by yuweih@chromium.org
, Apr 13 2018