This apparently wasn't well thought out. On important a file, it disables the dependent property if the prerequisite is not satisfied. But it doesn't change dynamically if the controlling property is changed. So it's better just to not have the feature at all, for now.
Fixing bug reported on github by srhinow, where setting Footer text to empty string does not get persisted.
Signed-off-by: Shane Bryan <email@example.com>
… integer properties
… by dragging delete button
Actually this bug is caused by a bug in jQuery UI sortable's _removeCurrentsFromItems. But if we make sure we don't have items in the currentItem, this bug will not be triggered. So I did the following to make this happen: * Make sure a sortable doesnt connect with the currentItem and its child sortables and update the items correctly after changing connectWith, * Make sure the items selector doesn't select unwanted items - The item selector of Navbar actaully makes Content select elements in a ThumbnailSplitList as items. This patch also fixes the problem that dragging a container may cause DOM hierachy error. This is because if the children in the currentItem is connected with the sortable, it's possible that the placeholder be put into the children of the currentItem and when dropping, jQuery UI will try to insert currentItem after/before placeholder, which will cause a DOM hierachy error.
…ing an event handler Fixed issue: https://01.org/jira/browse/RIB-37
…an those elsewhere. Fixed issue - https://01.org/jira/browse/RIB-40
In Google Chrome 15.0.874.121, the upload dialog can't show if we use the parent of the clicked item
Previous algorithm only supports one zone containers or Headers, and it works hard to determine the position for insertion. The new algorithm first tries to insert into the zone of the nearest sibling using enhanced insertChildAfter/Before; if it fails, it uses addChild to automatically find a zone to insert into.