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-tag: styleClass input not working #14020

Closed
lixaotec opened this issue Nov 3, 2023 · 6 comments
Closed

p-tag: styleClass input not working #14020

lixaotec opened this issue Nov 3, 2023 · 6 comments
Assignees
Labels
Resolution: Cannot Replicate Issue could not be replicated by Core Team Resolution: Needs Revision The pull request can't be merged. Conflicts need to be corrected or documentation and code updated. Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response

Comments

@lixaotec
Copy link

lixaotec commented Nov 3, 2023

Describe the bug

I´m trying to add custom color to tag just by adding new classes, and it seems the Input styleClass is not working, because i does not pass the classes i´ve entered

Environment

v16.6.0

Reproducer

No response

Angular version

16

PrimeNG version

16.6

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

latest

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

<span class that receives [class]="styleClass" should work.
Maybe its conclifting with the [ngClass]="computeClass()" that decides the severity

@lixaotec lixaotec 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 3, 2023
@lixaotec
Copy link
Author

lixaotec commented Nov 3, 2023

Also, it does not supports custom Severity... i think that would be great to accepts a custom severity

lets say: p-tag-{severity}
p-tag-plain
p-tag-ok

The whole concept of severity for all components could be more flexible

@cetincakiroglu cetincakiroglu modified the milestones: 16.Future, 16.8.0 Nov 16, 2023
@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 Nov 16, 2023
@mehmetcetin01140
Copy link
Contributor

Could you please share a stackblitz reproducer?

@mehmetcetin01140 mehmetcetin01140 added Resolution: Needs Revision The pull request can't be merged. Conflicts need to be corrected or documentation and code updated. Resolution: Cannot Replicate Issue could not be replicated by Core Team and removed Type: Bug Issue contains a bug related to a specific component. Something about the component is not working labels Nov 16, 2023
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.

@cetincakiroglu cetincakiroglu removed this from the 16.8.0 milestone Nov 16, 2023
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 Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response and removed Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response labels Mar 16, 2024
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 Jul 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 Jul 26, 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: Needs Revision The pull request can't be merged. Conflicts need to be corrected or documentation and code updated. 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
@lixaotec @cetincakiroglu @mehmetcetin01140 and others