Before this change the node that is displayed during a the last mouse
drag and drop would be listed in a keyboard drag and drop if it was
the container node of one of the types of node being moved in this action.
If a node is inside a node with the .yui3-dd-proxy class then it is
one of the proxy elements used to display the dragged content during
mouse drag and drop so we will start ignoring it.
Before this change sections and blocks could not be moved to be the
top item when using keyboard drag and drop.
They can now be moved to the top in one action.
The way they move using keyboard drag and drop has changed when they
are below the item they are dropped on, not instead of appearing
below it they will be placed above it.
Before this change keyboard drag and drop could not detect the
direction of movement, this meant that an item would only be placed
below an item or at the top of a container item.
This change means that extending modules can declare
detectkeyboarddirection to true. This will mean that when an item is
moved it's position will be determined by the direction of travel as
it would be when dragging using the mouse.
If detectkeyboarddirection is true then:
* If you move an item upwards it will be placed before the item
selected in the drop menu
* If you move a item downwards it will be placed after the item
selected in the drop menu
* The item above the one being dragged will now be displayed on
the drop menu
If detectkeyboarddirection is false there will be no change in
behaviour.
Before this change keyboard drag and drop of sections would alter
the structure of the page.
This occured because in this case the dragnode was the original node
Before this change when moving a section via drag and drop the
aria-label for the section was not being updated neither was the
title on the drag handle.
The result was the the drop menu on keyboard drag and drop displayed
the wrong information after a section was moved.
In MDL-67971, issuer_json.php was created, to display issuer JSON content.
However, some files were still using action=0 to display this information.
It has been replaced by issuer_json.php.
The action=0 support won't be removed (at least for now), because several
public badges URLs are using it.
Mozilla backpack closed a few months ago. It was moved to Badgr.io
(as OBv1.0) but as we're also supporting Badgr.io OBv2.0, it
makes no sense to leave old references to Mozilla backpack there.
