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

p-splitter: minSizes not working as expected #15943

Closed
MaSch0212 opened this issue Jul 2, 2024 · 0 comments · Fixed by #15944
Closed

p-splitter: minSizes not working as expected #15943

MaSch0212 opened this issue Jul 2, 2024 · 0 comments · Fixed by #15944
Labels
LTS-FIXED-15.4.22 LTS-FIXED-16.9.12 LTS-PORTABLE Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@MaSch0212
Copy link
Contributor

Describe the bug

When using the minSizes property on the p-splitter, the Splitter seems to always use the first two entries of the array.
Let's say I have 3 different panels and set minSizes to [15,35,50]:

  • When grabbing the first grabber (between panels 1 and 2) it works as expected
    • Panel 1 has a min size of 15% and Panel 2 has a min size of 35%
  • When grabbing the second grabber (between panels 2 and 3) it still uses the first two minSize values
    • Panel 2 can be reduced to 15% and Panel 3 has a min size of 35%

Environment

Windows 11
Firefox 128
Angular 17.3.11
PrimeNG 17.18.2

Reproducer

https://stackblitz.com/edit/github-2peuaj?file=src%2Fapp%2Fapp.component.html

Angular version

17.3.11

PrimeNG version

17.18.2

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

20.15.0

Browser(s)

Firefox 128

Steps to reproduce the behavior

  1. Add 3 panels to a p-splitter
  2. Set minSize with 3 different entries
  3. Resize the panels

Expected behavior

The minSizes should reflect the minimum sizes of each panel.

@MaSch0212 MaSch0212 added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jul 2, 2024
@cetincakiroglu cetincakiroglu added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Jul 4, 2024
@cetincakiroglu cetincakiroglu added this to the 17.18.3 milestone Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
LTS-FIXED-15.4.22 LTS-FIXED-16.9.12 LTS-PORTABLE Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants