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

Issue 788135 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Default focus is not seen on 'Restore' button of 'Restore pages' bubble.

Reported by db...@etouch.net, Nov 23 2017

Issue description

Chrome Version: 64.0.3276.0 Revision ccea2aa0a41cbb3dcbbf5961be4820d428b93a4c-refs/heads/master@{#518818}(32/64 bite)
OS: Windows(7,8,10), Linux(14.1LTS) 

What steps will reproduce the problem?
(1) launch chrome, crash browser using chrome://inducebrowsercrashforrealz
(2) Relaunch browser and observe default focus on 'Restore'.

Actual: Default focus on 'Restore' is not seen after relaunching browser.

Expected: Default focus on should seen on 'Restore' button.

This is a regression issue, broken in 'M64', will soon update the other info:

Good Build: 64.0.3270.0
Bad Build: 64.0.3271.0

Note: issue is not seen on mac Os.

 
Actual_Focus.mp4
304 KB View Download
Expected_Focus.mp4
287 KB View Download

Comment 1 by db...@etouch.net, Nov 23 2017

Labels: hasbisect-per-revision
Owner: hayato@chromium.org
Status: Assigned (was: Unconfirmed)
You are probably looking for a change made after 517325 (known good), but no later than 517327 (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/21a8455188c47f244a84413dde6e610da6f64a57..b431153dfba3fff0099e0403dfa12dea6ae174bd

Suspect: https://chromium.googlesource.com/chromium/src/+/21a8455188c47f244a84413dde6e610da6f64a57
Labels: ReleaseBlock-Stable
Adding Release blocker for this issue.Please undo if not the case.

Thank You!

Comment 3 by hayato@chromium.org, Nov 27 2017

Owner: db...@etouch.net
The suspect CL shouldn't be the cause because the CL is effective only when runtime flag IncrementalShadowDOM is on.

dbote@, could you find other suspect?


Comment 4 by db...@etouch.net, Nov 30 2017

Owner: futhark@chromium.org
With respect to comment 3:

Rebisected for the above issue, and getting below bisect range:
You are probably looking for a change made after 517139 (known good), but no later than 517140 (first known bad).

CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/491b1a06f7b2d32f35b45afdae622261193b77a9..6ddbf96264d611b883d034ed674e61031ab4151a

Suspect: https://chromium.googlesource.com/chromium/src/+/6ddbf96264d611b883d034ed674e61031ab4151a
Owner: db...@etouch.net
Reverting that change did not help (didn't expect that either). Bisect result sounds wrong.

Comment 6 by db...@etouch.net, Dec 5 2017

Owner: futhark@chromium.org
With respect to comment 5:

Re bisecting for the above issue and getting same result i.e.
CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/491b1a06f7b2d32f35b45afdae622261193b77a9..6ddbf96264d611b883d034ed674e61031ab4151a

Suspect: https://chromium.googlesource.com/chromium/src/+/6ddbf96264d611b883d034ed674e61031ab4151a

@futhark: Please help to assign this issue, if your change is not cause for it.

Owner: ----
Status: Available (was: Assigned)
I don't know who the be appropriate person would be.
Labels: -ReleaseBlock-Stable -hasbisect-per-revision Needs-Bisect
Status: WontFix (was: Available)
Tested the issue in chrome reported version #64.0.3276.0 and latest canary #65.0.3294.0 on win 7 and Ubuntu 14.04 and not able to reproduce the issue.Please find the screen cast for your reference.

Marking it as Wont Fix since issue is not reproduce in reported version and latest canary.Feel free to raise a new issue if still facing.

Thank you!
788135(Linux).ogv
3.1 MB View Download
788135(Win).mp4
506 KB View Download

Sign in to add a comment