Bug 73392 – REGRESSION:Deeply cloned nodes' style don't seem to listen to changes during drags

• Component: Layout and Rendering
• Status: NEW

[Dan Beam]

A recent WebKit roll in Chromium (http://crrev.com/111843) introduced an issue (http://crbug.com/105810) that causes clones of the source element to ignore style changes (i.e. changing draggingNode.cloneNode(true).style.left doesn't work).  One of these revs (http://goo.gl/FZnkK) introduced this.

Here are some simple test cases:
- using cloneNode - http://jsfiddle.net/wz384/9/
- using separate node - http://jsfiddle.net/wz384/13/

The manifestation of this bug is that dragging on the New Tab Page on Chrome 17.0.954.0 (today's Canary on MacOS) is broken as we're using a clone of the node a user originally dragged as a drag representation.  I've attached a screenshot to show what this looks like.  Notice that the mouse has started dragging but the clone isn't able to move like it used to (http://goo.gl/TveP5).

[Enclosure: chrome_new_tab_page_drag_representation_issue.png]

[Dan Beam]

Created attachment 117112 [details]
a screenshot of the manifestation of this issue

[Dan Beam]

This smells highly like a dupe of bug 73227.

[Andreas Kling]

(In reply to comment #2)
> This smells highly like a dupe of bug 73227.

I certainly agree with this assessment. Did you have a chance to verify that it got fixed?

[Dan Beam]

> I certainly agree with this assessment. Did you have a chance to verify that it got fixed?

We haven't rolled to/past the fixing rev (r101502).  We're still on r101316 at the moment (http://src.chromium.org/viewvc/chrome/trunk/src/DEPS?view=markup).