Investigation of the bug started with inspecting the browser DOM with the YUI code versus the non-YUI code. At first I thought it migt be a CSS flow issue where when one DIV is moved, the others might naturally flow from there too. But inspection showed that all of the DIVs were getting the same x,y coordinated. Them flowing is what made them show up in a row, instead of all on top of each otyher. The cssUpdate mechanism looked different between the two. Then I noticed that dragGhost was set in the non-YUI code, which might account for it acting differently. Sure enough, when using the same mode, they both exhibited the same bug. I investigated the decode method on the panelGroup to see if the cssUpdate was somehow being mis-applied to all of the rows, which is when I found that we don't do row state saving of the style properties, and that's why it was being applied to all rows. So I added all the style related properties to the row state saving, and that fixed it.

Subversion 19155
icefaces\component\src\com\icesoft\faces\component\ext\HtmlPanelGroup.java

To duplicate this, just take the component-showcase drag & drop example, and remove the dragGhost attribute, or turn it to false. If all of the panelGroups move, when you drag and drop one, then that's the bug. For automated testing, you can drag and drop one panelGroup, and test the style attribute of one of the non-dragged panelGroups to see if the x,y are being set.

Sorry, the attribute to remove is: dragOptions="dragGhost"

Mark confirmed that "item images stay at the dropping target area" is something expected without the dragGhost. Mark it as pass.