[Webkit-unassigned] [Bug 73392] New: Deeply cloned nodes' style don't seem to listen to changes during drags

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=73392

           Summary: Deeply cloned nodes' style don't seem to listen to
                    changes during drags
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
               URL: chrome://newtab
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Layout and Rendering
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: dbeam at chromium.org
                CC: dbeam at chromium.org


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]

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.