Skip to content

Commit b3bf320

Browse files
committed
Moved restriction text ➡️ implementation and drafted new restriction text 📝
1 parent c474dce commit b3bf320

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

recipe/0599-drag-and-drop/index.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,12 +15,11 @@ As a person wanting to annotate a IIIF resource, you would like to open a manife
1515

1616
## Implementation Notes
1717

18-
What do you need to know to use this pattern?
19-
How do you implement the pattern?
18+
Implementing this recipe requires a resource provider and a viewer provider each to implement their part. The resource provider must have a draggable item that can have a `dataTransfer.setData` method attached to the item's `dragstart` event and the viewer provider must have an interface capable of handling the data in its `drop` event.
2019

2120
## Restrictions
2221

23-
Implementing this recipe requires a resource provider and a viewer provider each to implement their part. The resource provider must have a draggable item that can have a `dataTransfer.setData` method attached to the item's `dragstart` event and the viewer provider must have an interface capable of handling the data in its `drop` event.
22+
Because implementation is two-part, you may only have control over one half of the ability to drag and drop. Consequently, and since this action is only in a GUI environment, you will need to consider whether visitors to your IIIF interface would benefit from some kind of support text.
2423

2524
## Example
2625

0 commit comments

Comments
 (0)