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

broken styles after updating from version 16.3.1 to 16.7.2 in angular #14072

Closed
beyaban opened this issue Nov 9, 2023 · 6 comments
Closed

broken styles after updating from version 16.3.1 to 16.7.2 in angular #14072

beyaban opened this issue Nov 9, 2023 · 6 comments
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@beyaban
Copy link

beyaban commented Nov 9, 2023

Describe the bug

The update from version 16.3.1 to 16.7.2 has completely messed up all the styles in my angular app. It doesn't make sense to fix all the styles manually. What has changed? Any ideas?

Environment

Angular 16.2.6, sass

Reproducer

No response

Angular version

16.2.6

PrimeNG version

16.7.2

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

v18.16.0

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

@beyaban beyaban 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 9, 2023
@imaksp
Copy link

imaksp commented Nov 9, 2023

styles for any specific component or all ? are you using custom theme?

@pete-mcwilliams
Copy link
Contributor

duplicate issue, it's to do with layers

@beyaban
Copy link
Author

beyaban commented Nov 10, 2023

styles for any specific component or all ? are you using custom theme?

styles for table, dropdown, input field, no custom theme defined

@beyaban
Copy link
Author

beyaban commented Nov 10, 2023

duplicate issue, it's to do with layers

what do you mean with layers?

@pete-mcwilliams
Copy link
Contributor

I mean search for the duplicate bug using the keyword layers #13757

@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,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

4 participants