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

Issue 792404 link

Starred by 2 users
Status: Fixed
Owner:
chrishtr@chromium.org
Closed: Mar 2018
Cc:
pdr@chromium.org
nyerramilli@chromium.org
rbasuvula@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
mac-bugs-priority@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:Favicon is seen after dragging app in chrome://apps after changing flag to RTL.

Reported by vku...@etouch.net, Dec 6 2017 
Chrome Version: 63.0.3239.84 8f51ed0e633e109109762a3deb18a50e8c138819-refs/branch-heads/3239@{#643}/master@{#521956}(64-bit)
OS: Mac (10.12.6) (10.13.2)

What steps will reproduce the problem?
(1)Launch chrome, navigate to chrome://flags and change 'Force UI direction' to 'Right-to-Left' and enable RTL flag
(2)Navigate to chrome://apps, drag multiple app and change the position 
(3)Observe the app while dragging 

Actual: Favicon is seen after dragging app in chrome://apps

Expected: Favicon should not be seen while dragging any app in chrome://apps

This is a regression issue broken in 'M63' and will soon update other info
Actual_Apps.mov
1.6 MB Download
Expected_Apps.mov
1.1 MB Download

Comment 1 by vku...@etouch.net, Dec 6 2017

Labels: hasbisect-per-revision
Owner: pdr@chromium.org
Status: Assigned (was: Unconfirmed)
Good Build: 63.0.3215.0  
Bad Build:  63.0.3216.0 

You are probably looking for a change made after 501850 (known good), but no later than 501851 (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/2700afca42099e3af0c2eed7a1fef7f1559c55d3..29a37905268827ff553fc2ba476ed3ed95b090b8

Suspecting: https://chromium.googlesource.com/chromium/src/+/29a37905268827ff553fc2ba476ed3ed95b090b8
Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Note: Issue not seen on Linux & Win OS.

Comment 2 by woxxom@gmail.com, Jan 3 2018 

The suspected CL also breaks another use case reported in  https://crbug.com/795966#c8  according to my bisect job:
https://chromium.googlesource.com/chromium/src/+log/f1400a36..49684282?pretty=fuller

Comment 3 by pdr@chromium.org, Mar 6 2018

Labels: Needs-TestConfirmation
I just got back from leave and found this bug. I am not able to reproduce it anymore, maybe it was fixed?

vkupte, could you confirm whether this was fixed?

Comment 4 by vku...@etouch.net, Mar 7 2018

Labels: -Needs-TestConfirmation
With respect to comment #3:

Rechecked above issue on latest canary version i.e 67.0.3364.0 (Official Build) on Mac(10.12.6, 10.13.1,10.13.4) OS and issue seems to be fixed.

Please refer attached screen-cast for reference
Actual_Mac.mov
3.1 MB View Download

Comment 5 by pdr@chromium.org, Mar 7 2018

Labels: Needs-Bisect
Can you bisect to see when this was fixed to see if we need to merge into beta?

Comment 6 by vku...@etouch.net, Mar 8 2018

Labels: -Needs-Bisect
With respect to comment # 5:

Below is the reverse bisect info:
You are probably looking for a change made after 526834 (known good), but no later than 526835 (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/40b0ca4848baaa1ff1c12632703747bf389260b0..16b3d20c33f49cc89d8f0b0c62cf93fde4675407

revision: https://chromium.googlesource.com/chromium/src/+/16b3d20c33f49cc89d8f0b0c62cf93fde4675407

Note: Issue got fixed from above mentioned revision i.e from 'M65' version no 65.0.3312.0 is a Good build onwards.

Comment 7 by pdr@chromium.org, Mar 8 2018

Cc: pdr@chromium.org
Owner: chrishtr@chromium.org
Status: Fixed (was: Assigned)
According to https://chromiumdash.appspot.com/commit/16b3d20c33f49cc89d8f0b0c62cf93fde4675407, this is in M65 so no merge is necessary.
►

Sign in to add a comment