HFP-3847 Improve draggable handling accessibility #149
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When merged in, will change how hovering a dropzone is detected to improve accessibility.
Currently, a dropzone is considered as being hovered based on the mouse pointer being over the dropzone, not the draggable. This can lead to situations where the draggable is in fact hovering the dropzone, suggesting it can be dropped, but the mouse pointer is not hovering the dropzone, the user releases the mouse button and the draggable is reverted to its original position instead of being dropped to the dropzone. This issue often happens when there's a dropzone on the first line, easily leading the mouse pointer getting set off the original drag position (cmp. e.g. https://h5p.org/node/1289113).
The behavior is changed by changing the jQueryUI
tolerance
option for droppables frompointer
totouch
and by disabling dropzones onover
events andout
events to prevent multiple dropzones from being highlighted when being hovered by a draggable at the same time.See ticket at https://h5ptechnology.atlassian.net/browse/HFP-3847