New issue
Advanced search Search tips

Issue 666590 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

"Display overscan" on-screen arrows remain on screen indefinitely after exiting the page

Project Member Reported by michae...@chromium.org, Nov 18 2016

Issue description

Not sure whether this is specific to CrOS on Linux, but:

1. chrome://md-settings/display
2. Tap to adjust overscan borders
3. Exit the page (back arrow, close the browser window, navigate to another website) without hitting "Save" or "Reset" on the overscan dialog

Expected: Overscan border arrows should disappears after leaving the Display sub-page
Actual: Overscan border arrows don't disappear even after closing the entire tab
 
Blocking: -614589
Status: Started (was: Assigned)
The back arrow works as expected for me. It is only when closing the tab/window that I can reproduce this in ToT.

Removing from blocking  issue 614589 .

Project Member

Comment 2 by bugdroid1@chromium.org, Dec 9 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/8f2b71add2ce71f468fb8274c20d7ea41d36886b

commit 8f2b71add2ce71f468fb8274c20d7ea41d36886b
Author: stevenjb <stevenjb@chromium.org>
Date: Fri Dec 09 03:21:11 2016

SystemDisplayApi: Introdice OverscanTracker

The system.display.overscanCalibrationStart method displays an overlay
for adjusting overscan when called.

If the web context initiating the call is deleted before
overscanCalibrationComplete is called, the overaly will remain with
no way to remove it (without running Settings or an app that shows
and removes the overaly correctly).

This change creates a tracker so that if the render frame is deleted
before overscanCalibrationComplete is called, the calibration will
be reset and completed to remove the overlay.

BUG= 666590 

Review-Url: https://codereview.chromium.org/2558453004
Cr-Commit-Position: refs/heads/master@{#437448}

[modify] https://crrev.com/8f2b71add2ce71f468fb8274c20d7ea41d36886b/extensions/browser/api/system_display/BUILD.gn
[modify] https://crrev.com/8f2b71add2ce71f468fb8274c20d7ea41d36886b/extensions/browser/api/system_display/system_display_api.cc
[modify] https://crrev.com/8f2b71add2ce71f468fb8274c20d7ea41d36886b/extensions/browser/api/system_display/system_display_apitest.cc
[add] https://crrev.com/8f2b71add2ce71f468fb8274c20d7ea41d36886b/extensions/test/data/system/display/overscan/manifest.json
[add] https://crrev.com/8f2b71add2ce71f468fb8274c20d7ea41d36886b/extensions/test/data/system/display/overscan/test_overscan.js
[add] https://crrev.com/8f2b71add2ce71f468fb8274c20d7ea41d36886b/extensions/test/data/system/display/overscan_no_complete/manifest.json
[add] https://crrev.com/8f2b71add2ce71f468fb8274c20d7ea41d36886b/extensions/test/data/system/display/overscan_no_complete/test_overscan_no_complete.js

Status: Fixed (was: Started)

Comment 4 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58
Status: Verified (was: Fixed)

Sign in to add a comment