-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 8
-
Component/s: client-libs
-
None
-
b06
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8045464 | 8u25 | Anthony Petrov | P3 | Resolved | Fixed | b01 |
| JDK-8031678 | 8u20 | Petr Pchelko | P3 | Resolved | Fixed | b01 |
| JDK-8053704 | emb-8u26 | Anthony Petrov | P3 | Resolved | Fixed | b17 |
Currently the DropTargetDropEvent.acceptDrop() method throws an exception if called multiple times while processing a single DnD event. Looking at its implementation it looks like there's no reason for this. The method only updates a few internal fields which are used when processing the dropComplete() operation. Therefore, before dropComplete() is invoked, the user code should be able to call the acceptDrop() method several times.
There's a JavaFX bug that depends on this possibility: https://javafx-jira.kenai.com/browse/RT-34283
There's a JavaFX bug that depends on this possibility: https://javafx-jira.kenai.com/browse/RT-34283
- backported by
-
JDK-8031678 Allow multiple calls to DropTargetDropEvent.acceptDrop()
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-