Drag handle improvements
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
If you drag an element into another element such as a list it's not a top level element anymore and therefore cannot be dragged anymore.
At first sight there seem to be two options to solve this:
- Do not allow dragging content into other elements - only allow sorting.
- Allow dragging subelements such as nested lists.
I don't know if 1. is feasible and it would of course reduce the usefulness of the feature - on the other hand it would also make it easier / more clear to use.
I don't know if 2. is feasible. It would be nice to be able to sort lists with this as well for example. But it's hard to destinguish if i want to drag the first list item or the entire list. I imagine there's more such questions this would raise due to the increased complexity.
Originally posted by @max-nextcloud in https://github.com/nextcloud/text/issues/7537#issuecomment-3195137387
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Start by locating the editor's drag-handle behavior and reproduce dragging a top-level element into a list, then assess the two proposed behaviors and their ambiguity for nested lists. Done means one behavior is selected, implemented, and covered by tests for dragging nested content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100