New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 680911 link

Starred by 1 user
Status: Fixed
Owner:
foolip@chromium.org
Closed: Jan 2017
Cc:
nyerramilli@chromium.org
rbasuvula@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression

Blocking:
issue 402376



Sign in to add a comment

Regression:Page appears to be auto scrolled after exiting Full screen in "www.quirksmode.org"

Reported by adha...@etouch.net, Jan 13 2017 
Chrome Version: 57.0.2980.0 (Official Build)6770bab14919fc9abed1d457387824e84cc43602-refs/heads/master@{#443474} 32/64-bit.
OS: Windows(7,8,10), Mac (10.11.6, 10.12.1), Linux (14.04 LTS).

Test url:http://www.quirksmode.org/html5/tests/video.html

What steps will reproduce the problem?
(1)Launch chrome chrome,navigate to the above url.
(2)Scroll down the page and play the last video.
(3)Resize the browser window and click on Full screen icon of the video.
(4)Press Esc key and observe.(Kindly refer the video)

Actual:Page appears to be auto scrolled after exiting Full screen.

Expected:Page should not seem to auto scroll after exiting Full screen.

This is a Regression issue broken in M-57,will soon update other info.

Good build:57.0.2956.0
Bad build:57.0.2957.0
Actual result.mp4
1.4 MB View Download
Expected result.mp4
1.2 MB View Download

Comment 1 by rbasuvula@chromium.org, Jan 13 2017

Cc: rbasuvula@chromium.org
Labels: hasbisect-per-revision
Owner: foolip@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build: 57.0.2956.0 (Revision: 439388).
Bad build: 57.0.2957.0 (Revision: 439663).

You are probably looking for a change made after 439606 (known good), but no later than 439607 (first known bad).

CHANGE-LOG URL:
---------------
https://chromium.googlesource.com/chromium/src/+log/c689031affc2246cb94c98a707d5ab7c7b737993..e1d42d636990425056ede44086ef49a1f8c6a0a5

From the CL above, assigning the issue to the concern owner

@foolip: 
------------------
Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Review-Url: https://codereview.chromium.org/2573773002

Note: Able to reproduce the issue in Ubuntu 14.04,Win 10.0 & mac 10.12.2.

Comment 2 by rbasuvula@chromium.org, Jan 13 2017

Labels: OS-Linux

Comment 3 Deleted

Comment 4 by foolip@chromium.org, Jan 19 2017 

Just confirming that I have seen this and that it's very plausible, almost certain, that my CL is to blame. I will look into this after handling two more urgent regressions on M-56.

Comment 5 by foolip@chromium.org, Jan 25 2017 

Just an update that I won't have time to fix this until after BlinkOn. There should still be time then and I am reluctant to revert in the interim as  issue 240576  depends on this change remaining, so it's worth holding out a bit longer I think.

Comment 6 by foolip@chromium.org, Jan 26 2017

Blocking: 402376

Comment 7 by foolip@chromium.org, Jan 31 2017

Status: Fixed (was: Assigned)
Fixed by reverting "Sync requestFullscreen() and exitFullscreen() algorithms with the spec"

Comment 8 by foolip@chromium.org, May 4 2017 

I made some changes in https://codereview.chromium.org/2855843002/ (reland of  issue 402376 ) to address  issue 680467  and have confirmed that those same changes also make the difference between this regression happening and not happening.

I haven't minified the page to find out why.
►

Sign in to add a comment