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

Issue 808363 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jul 2
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Unnecessary traces of window is seen when device is in tablet mode in chrome://settings

Project Member Reported by kebalaji@chromium.org, Feb 2 2018

Issue description

Chrome Version: 65.0.3325.39/10323.12.0 Dev channel Cyan
OS: Chrome OS

What steps will reproduce the problem?
(1)Sign-in to user>> Flip the device to tablet mode>> Navigate to chrome://settings
(2) Touch on Add wifi>> Now type something in SSID field and try scrolling the WiFi overlay and observe

Actual: Unnecessary traces of window is seen 
Expected: No such traces should be seen

This is a Regression issue as same is working fine on M64 Beta

NOTE: Issue is touch device specific.


 
ActualWifi.mp4
3.5 MB View Download
ExpectedWifi.mp4
3.2 MB View Download
Labels: Inhouse-HYD-Reported
Cc: xiy...@chromium.org steve...@chromium.org
Owner: osh...@chromium.org
This doesn't seem specific to the UI dialog, but maybe we are doing the window frame incorrectly?

oshima@, who should own this?

Owner: wutao@chromium.org
looks like compositor issue. kebalaji@, can you narrow down the regression range?

wutao@ can you bisect based on the range?

Comment 4 by wutao@chromium.org, Feb 6 2018

Bisecting now, I am thinking this is caused by some cl removed the stick header of the wifi window.
C #3 >
Unable to provide bisect as we dont have bisect setup available on Chrome OS to bisect the issue.

The issue seems to regressed around :
Good Build:64.0.3282.144/10176.68.0
Bad Build :65.0.3325.39/10323.12.0 Dev

Thanks!

Comment 6 by wutao@chromium.org, Feb 7 2018

I also saw this on M66 ToT.

When the wifi UI dialog has sticky header, then it is fine, when there is no the sticky header, the bug exist. In the range of R66-10356.0.0 to R66-10369.0.0

Will continue bisect.

Comment 7 by wutao@chromium.org, Feb 17 2018

This is fixed at ToT.
Please verify.
Status: Fixed (was: Assigned)

Sign in to add a comment