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

Toggleable fieldset inside another toggleable fieldset has its content visible when collapsed by deafult #11736

Closed
majkers opened this issue Jul 25, 2022 · 11 comments · Fixed by #12146
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@majkers
Copy link

majkers commented Jul 25, 2022

Describe the bug

When one toggleable fieldset has another toggleable fieldset inside and thay are both collapsed by default, and when expanding the first one, then the content of the inner one is visible even though it is collapsed.

Environment

Angular 14.1
PrimenNG 14
Windows

Reproducer

https://stackblitz.com/edit/github-trkcts-tjm2ed?file=src/app/app.component.html

Angular version

14.1.0

PrimeNG version

14.0.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

14.17.3

Browser(s)

Chrome 103.0.5060.134

Steps to reproduce the behavior

  1. go to https://github-trkcts-tjm2ed.stackblitz.io/ or https://stackblitz.com/edit/github-trkcts-tjm2ed?file=src/app/app.component.html
  2. expand first fieldset
  3. second fieldset is collapsed and its content is visible

Expected behavior

The content of second fieldset should be hidden when fieldset is collapsed.

The problem is when toggleable fieldset are nested one inside another.

This css is wrong:

.p-fieldset-toggleable.p-fieldset-expanded .p-toggleable-content:not(.ng-animating) {
    overflow: visible;
}
@majkers majkers added the Type: Bug Issue contains a bug related to a specific component. Something about the component is not working label Jul 25, 2022
@Smorgaz
Copy link

Smorgaz commented Jul 25, 2022

The same error applies to panels, accordions and panelmenus and was introduced in commit f849e9d.

@majkers
Copy link
Author

majkers commented Aug 17, 2022

Any news on that? I can't migrate to Angular 14 because of that.

@Vernon-Accela
Copy link

Seeing this on nested p-panels. I've had to write ng-deep css to override it until a fix can be delivered

@majkers
Copy link
Author

majkers commented Aug 23, 2022

Might be fixed in 14.0.2 as #11848 got closed with #11856 at least for accordion

@krtek4
Copy link

krtek4 commented Sep 13, 2022

The fix for #11848 broke dropdowns inside accordions.

If a dropdown is bigger than the size of the accordion, its content isn't displayed entirely.

Instead of just removing the buggy css, something like that could be done :

.p-accordion-tab-active > .p-toggleable-content:not(.ng-animating) {
  overflow: visible;
}

@rosenthalj
Copy link
Contributor

rosenthalj commented Sep 13, 2022

The fix for #11848 broke dropdowns inside accordions.

If a dropdown is bigger than the size of the accordion, its content isn't displayed entirely.

Instead of just removing the buggy css, something like that could be done :

.p-accordion-tab-active > .p-toggleable-content:not(.ng-animating) {
  overflow: visible;
}

Did you mean:

.p-accordion-tab-active > .p-toggleable-content:not(.ng-animating) {
    overflow: unset;
}

This change corresponds to the workaround I provided for bug #11924

@mertsincan
Copy link
Member

Hi,

So sorry for the delayed response! Improvements have been made to many components recently, both in terms of performance and enhancement. Therefore, this improvement may have been developed in another issue ticket without realizing it. You can check this in the documentation. If there is no improvement on this, can you reopen the issue so we can include it in our roadmap?
Please don't forget to add your feedback as a comment after reopening the issue. These will be taken into account by us and will contribute to the development of this feature. Thanks a lot for your understanding!

Best Regards,

@majkers
Copy link
Author

majkers commented Nov 10, 2022

Still exist in 14.2

https://stackblitz.com/edit/primeng-password-demo-4mrybd?file=src/app/app.component.ts

@majkers
Copy link
Author

majkers commented Nov 10, 2022

@mertsincan I can't reopen issues

@mertsincan mertsincan reopened this Nov 11, 2022
@github-actions github-actions bot added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Nov 11, 2022
@cetincakiroglu
Copy link
Contributor

cetincakiroglu commented Nov 11, 2022

Hi @majkers,

The reproducer project is broken could you please update it so I can check?

The error I got;

Import error, can't find file:
/src/styles.css

@cetincakiroglu cetincakiroglu removed the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Nov 11, 2022
@cetincakiroglu cetincakiroglu added this to the 14.2.2 milestone Nov 11, 2022
@majkers
Copy link
Author

majkers commented Nov 11, 2022

@cetincakiroglu did you check link from my last comment? https://stackblitz.com/edit/primeng-password-demo-4mrybd?file=src%2Fapp%2Fapp.component.ts It is working just fine and is build with latest angular and PrimeNg

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
None yet
Development

Successfully merging a pull request may close this issue.

7 participants