Community
Participate
Working Groups
Build Identifier: SWT 3.6 When XULRunner or an ancestor of XULRunner is disabled, drops do not work as expected. 1. When the dragged data is provided by the same application, XULRunner does not accept the drop but eats it even when an enabled ancestor accepts drops. 2. When the dragged data is provided by an external application (dragging words from a text editor), XULRunner accepts the drop. The correct behavior should be that dropped data gets ignored by XULRunner and in all cases passed to the closest enabled ancestor that is a drop target (if any). I believe it only affects a limited number of users, but I know a few of them who require a fix because it is a showstopper for their Linux deployment. Reproducible: Always Steps to Reproduce: cf attachement
Created attachment 176061 [details] Disabled hierarchy on a XULRunner browser with a draggable label. When dragging and dropping data, maintain the "control" key down, otherwise it is normal for the drag to be rejected (only accept copy). The attachment contains a label to test dropping data from the same application. You would need to test from an external application too. This was found with XULRunner 1.9.2.6 on Ubuntu.
More info: - WebKit does not have the issue. - IE and XULRunner 1.9.0.3 on Windows do not have the issue.
Xulrunner is being phased out so this bug will not be fixed.
