New issue
Advanced search Search tips

Issue 850097 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

the buttons around the omnibox showing a square ripple effect in the flag chrome://flags/#top-chrome-md

Reported by aakashsi...@gmail.com, Jun 6 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.62 Safari/537.36

Steps to reproduce the problem:
hover or click the buttons on or around the omnibox

What is the expected behavior?
there must be a circular ripple effect instead of square

What went wrong?
the buttons around the omnibox showing a square ripple effect in the flag chrome://flags/#top-chrome-md
but after toggling this the ripple effect must appear as a circle
the view site info button looks odd due to this fault the omnibox edges are round but the button is showed as a square

Did this work before? N/A 

Chrome version: 67.0.3396.62  Channel: stable
OS Version: 10.0
Flash Version:
 
clip.mp4
46.8 KB View Download
Cc: susan.boorgula@chromium.org
Labels: Triaged-ET Needs-Bisect Needs-Triage-M67
Status: Untriaged (was: Unconfirmed)
aakashsingh1407@ Thanks for the issue.

Able to reproduce this issue on Windows 10 on the latest Stable 67.0.3396.79.
Unable to reproduce the issue on Latest Beta 68.0.3440.17 and Canary 69.0.3452.0.
Issue is not observed on Mac OS 10.13.3 and Ubuntu 17.10.

Hence marking this issue as Untriaged. Will provide the bisect information soon.

Thanks...
Cc: pbomm...@chromium.org
Labels: -Type-Bug -Pri-2 -Needs-Bisect ReleaseBlock-Stable RegressedIn-67 Target-67 FoundIn-67 hasbisect Pri-1 Type-Bug-Regression
Owner: pbos@chromium.org
Status: Assigned (was: Untriaged)
// Adding to comment #1

Able to reproduce this issue on Windows 10 on the latest Stable 67.0.3396.79 by setting the #top-chrome-md flag to 'Refresh'.
Issue seems to be fixed on the latest Beta 68.0.3440.17 and Canary 69.0.3453.0.

Reverse Bisect Information:
============================
Good Build: 68.0.3397.0 
Bad Build : 67.0.3396.82 

Below is the changelog URL from Omahaproxy, as the bad build is a branch build.

https://chromium.googlesource.com/chromium/src/+log/67.0.3396.0..68.0.3397.0?pretty=fuller&n=10000

From the above Changelog, suspecting the below change:
Reviewed-on: https://chromium-review.googlesource.com/999113

pbos@ Please check and confirm if this issue is related to your change, else help us in assigning to the right owner.

Adding ReleaseBlock-Stable as this is a recent regression. Please feel free to remove if it is not applicable.

Thanks

Comment 3 by ajha@chromium.org, Jun 11 2018

Labels: M-67

Comment 4 by gov...@chromium.org, Jun 11 2018

Labels: -M-67 -Target-67 M-69 M-68 Target-68 Target-69
Per comment #2, we need to enable flag to repro this and M67 stable is out since 05/29. We're not going to block M67 further roll out for this.

Comment 5 by pbos@chromium.org, Jun 11 2018

Status: WontFix (was: Assigned)
This experimental flag is not targeting M67 and isn't broken after that, WontFix'ing.

Comment 6 Deleted

as per comment #2 i tried to update my browser but its saying
Google Chrome is up to date
Version 67.0.3396.79 (Official Build) (32-bit)
how should i get Version 68.0.3397.0 (Official Build)

Comment 8 by pbos@chromium.org, Jun 12 2018

M67 is the stable version of Chrome, if you want to run newer (but unstable) versions of Chrome, see: https://www.chromium.org/getting-involved/dev-channel

M68 is the current Beta version, M69 is Dev. These are less-tested preview versions of Chrome so you can expect them to be less stable (crash more, have more bugs).

Note that the Refresh mode that you're using is still under development and currently not really supported in any channel.

Sign in to add a comment