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

Issue 849186 link

Starred by 1 user
Status: WontFix
Owner:
█ vabr@chromium.org
hobby only
Closed: Jun 2018
Cc:
tommycli@chromium.org
nyerramilli@chromium.org
rbasuvula@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:Password bubble appears to be chopped from bottom after clicking on 'save' button.

Reported by vku...@etouch.net, Jun 4 2018 
Chrome Version: 69.0.3449.0 (Official Build)Revision 4c662013d5fa1e3a073c4e2a62844d6838d152d3-refs/branch-heads/3449@{#1} (32/64-bit)
OS: Win(7,8,8.1,10)

What steps will reproduce the problem?
(1)Launch chrome and navigate to any website for e.g https://twitter.com/ or http://gmail.com/
(2)Login with valid credentials such that password bubble appears.
(3)Now click on save button and observe.

Actual: Password bubble appears to be chopped from bottom after clicking on 'save' button.

Expected: Password bubble should be properly (i.e completely) displayed after clicking on 'save' button.

This is a regression issue broken in 'M69' and below is the manual bisect info
Good Build: 69.0.3447.0 (Revision:563479)
Bad Build:  69.0.3448.0 (Revision:563958)

Note: Will soon update other OS info.
Password bubble.png
164 KB View Download

Comment 1 by vku...@etouch.net, Jun 4 2018

Labels: RegressedIn-69 FoundIn-69 Target-69 hasbisect
Owner: vabr@chromium.org
Status: Assigned (was: Unconfirmed)
(Unable to narrow down the range using per-revision bisect,hence providing bisect using old script)
Narrow Bisect info:
You are probably looking for a change made after 563674 (known good), but no later than 563689 (first known bad).
CHANGELOG URL:
https://chromium.googlesource.com/chromium/src/+log/bdb4a42cda67aad4c162352f9d51325d4e48be7d..1148adfd2d6f3dae35aaa9973a08de3668855bbc?pretty=fuller&n=30

Suspecting: r563687 ?

@vabr: 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 not seen on Mac OS X(10.12.6,10.13.1,10.13.6) & Linux (14.04 LTS) OS.
Actual.mp4
513 KB View Download

Comment 2 by pnangunoori@chromium.org, Jun 5 2018 

Tested on Corp and Non-Corp machines and was not able to reproduce the issue on clean profiles using Chrome #69.0.3449.0. Attached the GPU of Non-corp machine's.

vkupte@ -- Could you please attach the GPU of your machine.

Thanks!
Chrome-GPU-TestMachine.txt
12.0 KB View Download

Comment 3 by vku...@etouch.net, Jun 5 2018 

With respect to comment #2:

Update:

Rechecked above issue on latest canary 69.0.3450.0 (Official Build) and the issue is fixed and working as intended hence done the reversed bisect for this issue using Bad Build: 69.0.3449.0(Revision:563986) and Good Build: 69.0.3450.0(Revision:564323), below is the bisect info:

https://chromium.googlesource.com/chromium/src/+log/b3d3db3f47c6cb83b9897fb8d33874b958b2a276..e1e4e8409b0cee3d1ac7d343cd7d69b4b6880bdb?pretty=fuller&n=30

Suspect: https://chromium.googlesource.com/chromium/src/+/5cab33d1317a67d2512b8677a91611b5b5d18d91

Comment 4 by vabr@chromium.org, Jun 5 2018

Cc: tommycli@chromium.org
Thanks for the updates.

r563687 is definitely not related (it renames some unrelated build targets).

Cc-ing the author of the CL mentioned in #3, although I suspect we can close this given that #3 confirms this being fixed in latest Canary?

Comment 5 by vabr@chromium.org, Jun 5 2018

Status: WontFix (was: Assigned)
Actually, let me close this. Please reopen if the issue is still observable.
►

Sign in to add a comment