3. Add in an option "fixed". When we have "submit all and finish" we don't want to allow users to then drag things. This is an edge case for after the quiz. I think we can achive this by adding in an argument to the JSON in the student's input "fixed", and this will get sent to the block. We can talk about this.
1. Add in an option "fixed". When we have "submit all and finish" we don't want to allow users to then drag things. This is an edge case for after the quiz. I think we can achive this by adding in an argument to the JSON in the student's input "fixed", and this will get sent to the block. We can talk about this.
4. Polish up the "use once" or "clone" strings.
2. Polish up the "use once" or "clone" strings.
5. Confirmation for delete all?
3. Confirmation for delete all?
6. Use syntax hint to set up a non-empty starting point....
4. Use syntax hint to set up a non-empty starting point....
7. Check sortable for keyboard accessibility*
5. Check sortable for keyboard accessibility (Not build in to Sortable currently: https://github.com/SortableJS/Sortable/issues/1951; however, it looks like it is do-able with some work https://robbymacdonell.medium.com/refactoring-a-sortable-list-for-keyboard-accessibility-2176b34a07f4)