Community
Participate
Working Groups
Currently you can drag incoming additions into the editor area and a blank editor is opened instead of the remote. We should disallow this case.
consider for M2
3.0 When you drag non-existing resource into the resource navigator dropping is disabled. However, when dropping into the editor area it is enabled. This seems inconsistent. Also, when a non-existing resource is dragged into the editor area a new file buffer is created, then when saved, doesn't show up as a resource in the navigator. To reproduce, generate an incoming addition in the synchronize view, then drag that element around. We don't want to disable dragging on non-existing resources from the sync view because several of our views accept that case.
Comitted in >20071114. No longer attempt to open the file but we still show the drop affordance. Duong, when I'm handling the 'dragEnter'/'dragOver' events the event.data field is null; is there any way to get the data in either of these methods?
On some platforms (eg. Windows) the data is null until a drop occurs. The Windows implementation prevents data from being copied by the source prematurely.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
