Splitter: Resize not stopped at limits when using more than 2 vertical panels

Open
#8,432 0 comments 0 reactions 0 assignees View on GitHub

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

Status: Needs Triage
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
  1. Open the linked Stackblitz project.
  2. 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

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 primefaces/primereact

All issues in primefaces/primereact

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.