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-selectButton: Can not add a overwritten class #14647

Closed
ClaraKrchr opened this issue Jan 29, 2024 · 4 comments
Closed

p-selectButton: Can not add a overwritten class #14647

ClaraKrchr opened this issue Jan 29, 2024 · 4 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

@ClaraKrchr
Copy link

Describe the bug

I'm working on prime ng in v16, before the version update of angular (I'm now in v16) I was working on a p-selectButton which had a different background color depending on the id of the displayed object. Since the migration, my buttons no longer change color, I no longer even see my class in the DOM.
I contacted the prime ng discord, they told me it was a regression and to create an issue ticket here

Environment

I work on visual studio code and with edge.

Reproducer

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

Angular version

16.2.10

PrimeNG version

16.5.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

16.16.0

Browser(s)

edge

Steps to reproduce the behavior

just open the DOM and you will not see my class

Expected behavior

No response

@ClaraKrchr ClaraKrchr added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jan 29, 2024
@zzzaaa
Copy link
Contributor

zzzaaa commented Jan 29, 2024

Your example doesn't work (compile error) You forgot to attach a models array. :)

@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 Feb 5, 2024
Copy link

github-actions bot commented Feb 5, 2024

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

github-actions bot commented Jun 5, 2024

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 Jun 5, 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 Jun 12, 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

3 participants