ASAP Problem with deleting absoluted positioned Components

Open
#323 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, react
Domain
frontend

Research direction

Start by reproducing the behavior with more than two absolutely positioned components, then delete a non-final element and observe how the remaining components move. The issue does not name a file or test; done means deleting any element leaves every other element at its existing position.

Written by the indexing model from the issue text.

Description

The problem is that i have >2 elements. When i delete not the last element, the other move out to get other element place.
I do not need that behavior. I want each element stay at its place.
Is it availiable to be fixed? Or is there a solution on this case?

ASAP

Dominant language
JavaScript
Stars
9.3k
Forks
1k
Avg merge
3d 8h
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from react-grid-layout/react-draggable

All issues in react-grid-layout/react-draggable

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.