Splitter: Resize not stopped at limits when using more than 2 vertical panels
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- react
- Domain
- frontend
Research direction
Start with the linked StackBlitz reproducer, especially src/App.jsx, and reproduce the issue with more than two vertical panels. Trace the resize behavior from the panel and handle setup; done means dragging beyond either limit leaves panel sizes stable and a later resize does not visibly jump.
Written by the indexing model from the issue text.
Description
Describe the bug
When using more than 2 vertical panels, dragging the resize handle beyond the top or bottom limit results in all panels being slightly resized. Later, on the next resize operation, panel sizes might appear to "jump" when starting the drag.
Reproducer
https://stackblitz.com/edit/goyghi6w?file=src%2FApp.jsx
System Information
System:
OS: Linux 6.14 Ubuntu 24.04.3 LTS 24.04.3 LTS (Noble Numbat)
CPU: (6) x64 Intel(R) Core(TM) Ultra 7 258V
Memory: 8.52 GB / 11.68 GB
Container: Yes
Shell: 5.2.21 - /bin/bash
Binaries:
Node: 25.0.0 - /home/x/.nvm/versions/node/v25.0.0/bin/node
npm: 11.6.2 - /home/x/.nvm/versions/node/v25.0.0/bin/npm
bun: 1.3.0 - /home/x/.local/share/reflex/bun/bin/bun
Browsers:
Chromium: 143.0.7499.40
Firefox: 146.0
Firefox Developer Edition: 146.0
npmPackages:
primereact: ^10.9.7 => 10.9.7
react: ^19.2.0 => 19.2.0
tailwindcss: ^4.0.6 => 4.1.15
Steps to reproduce the behavior
- Open the linked Stackblitz project.
- Drag any of the resize handles beyond the top or bottom limit.
Expected behavior
No response
- Dominant language
- CSS
- Stars
- 8.3k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from primefaces/primereact
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
primefaces/primereact#8552 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
primefaces/primereact#8550 ·
-
Row checkbox selection tick is invisible in Landing Page Theme sectionPossibly taken @Prakash1185 claimed this 173 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
primefaces/primereact#8545 ·
-
Dependency conflict between jspdf v4 and jspdf-autotable during npm installPossibly taken @Kamran92 claimed this 187 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
primefaces/primereact#8537 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
primefaces/primereact#8551 ·
All issues in primefaces/primereact
Similar issues
-
[BUG]: Shared links drop the configured basePath on GitHub PagesPossibly taken @anshulchikhale30-p claimed this today. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
StabilityNexus/IdentityTokens-EVM-Frontend#182 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 Under an hour Newbie friendliness 82/100
Leonxlnx/taste-skill#216 ·
Maintainers usually reply within 1 day
-
area: ui Bug Payload OSS
Difficulty 1/5 Under an hour Newbie friendliness 88/100
payloadcms/payload#19839 ·
Maintainers usually reply within 1 day
-
BoxShadow.lerp returns the wrong blur style at t = 0 or t = 1Possibly taken @ArtemChikolaev claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day