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

Issue 714457 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

When dragging a rotated element the ghost image does not show the rotation

Reported by dan.dumb...@gmail.com, Apr 23 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36

Steps to reproduce the problem:
1. Load the attached html file in chrome
2. Drag the "Drag Me!" box
3. 

What is the expected behavior?
The ghost image shows the rotation of the element being dragged

What went wrong?
The ghost image has no rotation

Did this work before? Yes 50.0.2661.75

Does this work in other browsers? Yes

Chrome version: 58.0.3029.81  Channel: stable
OS Version: OS X 10.12.1
Flash Version: Not enabled
 
dragtest.html
380 bytes View Download
Screen Shot 2017-04-23 at 12.47.55 PM.png
37.3 KB View Download
Labels: Needs-Bisect Needs-Triage-M58
Cc: brajkumar@chromium.org
Labels: -Needs-Bisect -Needs-Triage-M58 M-60 hasbisect
Owner: pdr@chromium.org
Status: Available (was: Unconfirmed)
Able to reproduce on Windows 10, Ubuntu 14.04 and Mac OS 10.12.4 using chrome stable M58-58.0.3029.81.

Bisect Information:
=====================
Good build: 50.0.2626.0 
Bad Build : 50.0.2628.0 

You are probably looking for a change made after 370457 (known good), but no later than 370478 (first known bad).

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/064741fcce814e441ee88f0230ca8066c4192049..89b8559b921b3a523dea4c7002cb79e2531579c3

From the above change log suspecting below change
Review URL: https://codereview.chromium.org/1610233002

pdr@ - 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.

Thanks!
Labels: -Type-Bug-Regression -M-60 BugSource-User PaintTeamTriaged-20170424 Type-Bug
Something that regressed in M-50 is not a current regression.
Status: Assigned (was: Available)
Per discussion, I think this is a WontFix.

Comment 5 by pdr@chromium.org, Apr 25 2017

Thanks for filing with a nice and small testcase. This is possible to work around (http://jsbin.com/surojo) but I think it may have been an oversight in the original patch. Lets leave it assigned to me for now.
You're welcome for the small testcase.  I've dealt with my fair share of bad ones.

Thanks for the quick response and the workaround.

Sign in to add a comment