shakacode / shakacode/rescript-dnd
Drop target size is inconsistent depending on if source is self or other.
Open
Nobody has claimed this yet.
- Dominant language
- ReScript
- Stars
- 119
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Note how easily Todo 11 can be dropped at the end of List 2 whenever it started its drag from List 2. When the drag starts from List 1 however, the drop zone is only the size of the original element, it does not expand to the visible element size.
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
Reproduce the Todo 11 drag from List 1 and List 2, comparing the drop zone at the end of List 2 as shown in the linked GIF. Trace the drag-source and drop-target handling to identify why the visible element size differs by source list. Done means both paths expose the same drop-target size and the reported behavior no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100