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

All Components: Styles broken #15151

Closed
notzairdev opened this issue Mar 24, 2024 · 6 comments
Closed

All Components: Styles broken #15151

notzairdev opened this issue Mar 24, 2024 · 6 comments
Labels
Resolution: Cannot Replicate Issue could not be replicated by Core Team Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response

Comments

@notzairdev
Copy link

Describe the bug

I have updated my PrimeNG components to the latest version but my styles are broken, both for the ContextMenu, MultiSelect, etc. I am using Angular 17.2.1 with the latest version of PrimeNG

image

Environment

localhost and my web deployments

Reproducer

No response

Angular version

17.2.1

PrimeNG version

17.12.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

21.2.0

Browser(s)

Google Chrome 123.0.6312.58

Steps to reproduce the behavior

No response

Expected behavior

No response

@notzairdev notzairdev added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Mar 24, 2024
@khaldi-yass
Copy link

Indeed, every dropdown components is now broken after upgrading with a left padding.

@jacqueslareau
Copy link

Cannot upgrade primeng anymore, critical bugs on each version update

@notzairdev
Copy link
Author

And downgrading the version to version 15, which is the one that works best, gives me problems with NPM and I have to force everything.

@mehmetcetin01140 mehmetcetin01140 added Resolution: Cannot Replicate Issue could not be replicated by Core Team and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels May 17, 2024
Copy link

We're unable to replicate your issue, if you are able to create a reproducer by using PrimeNG Issue Template or add details please edit this issue. This issue will be closed if no activities in 20 days.

Copy link

This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment!

@github-actions github-actions bot added the Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response label Sep 15, 2024
Copy link

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you for your understanding!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Cannot Replicate Issue could not be replicated by Core Team Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response
Projects
None yet
Development

No branches or pull requests

4 participants