Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SplitterPanel: Exceeds minSize on Subsequent Drags #7001

Closed
raptium opened this issue Dec 25, 2024 · 1 comment · Fixed by #7099
Closed

SplitterPanel: Exceeds minSize on Subsequent Drags #7001

raptium opened this issue Dec 25, 2024 · 1 comment · Fixed by #7099
Assignees
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@raptium
Copy link

raptium commented Dec 25, 2024

Describe the bug

When using a SplitterPanel with a defined minSize, the panel correctly stops resizing at the minimum size during the first drag. However, after releasing the mouse, dragging the gutter again allows the panel to exceed the minSize by a few pixels with each attempt.

Reproducer

https://stackblitz.com/edit/lsrnxm-pabadbps?file=src%2FApp.vue

PrimeVue version

4.2.5

Vue version

3.x

Language

TypeScript

Build / Runtime

Vite

Browser(s)

No response

Steps to reproduce the behavior

  1. Create a SplitterPanel and set a minSize for one of the panels.
  2. Drag the gutter to decrease the panel size until it reaches the minSize.
  3. Release the mouse button.
  4. Drag the gutter again and observe that the panel can exceed the minSize by a few pixels.
  5. Repeat the drag action to see the same behavior.

Expected behavior

The panel should not resize beyond the minSize after the initial drag.

@raptium raptium added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Dec 25, 2024
@cagataycivici cagataycivici added Resolution: Help Wanted Issue or pull request requires extra help and feedback good first issue *** Welcome to PrimeVue Family! *** Good issue! labels Dec 27, 2024
Copy link

Due to PrimeVue team's busy roadmap, this issue is available for anyone to work on. Make sure to reference this issue in your pull request. ✨ Thank you for your contribution! ✨

@mertsincan mertsincan added this to the Future milestone Jan 6, 2025
@mertsincan mertsincan removed the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jan 6, 2025
@github-project-automation github-project-automation bot moved this to Review in PrimeVue Jan 6, 2025
@tugcekucukoglu tugcekucukoglu added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working and removed good first issue *** Welcome to PrimeVue Family! *** Good issue! labels Jan 15, 2025
@tugcekucukoglu tugcekucukoglu modified the milestones: Future, 4.3.0 Jan 15, 2025
@tugcekucukoglu tugcekucukoglu self-assigned this Jan 15, 2025
@github-project-automation github-project-automation bot moved this from Review to Done in PrimeVue Jan 15, 2025
@mertsincan mertsincan removed the Resolution: Help Wanted Issue or pull request requires extra help and feedback label Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants