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

TypeError: Click listener in primeng StyleClass throws a null object error #14963

Closed
adri95cadiz opened this issue Mar 7, 2024 · 1 comment
Closed
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@adri95cadiz
Copy link

Describe the bug

This happens sometimes when the click listener is triggered and the target is not in the dom anymore, I'm unable to reproduce this issue in a controlled environment as it only happens on complex interfaces with many mutations.

Nevertheless the error seems easy to fix as it is checking if (this.target.offsetParent === null) and it could be controlled if the target is not existant anymore to avoid triggering these kinds of issues.

Environment

This is an angular application on PrimeNG version 17.8.0 but it has been happening since PrimeNG 16.

Reproducer

No response

Angular version

17.2.*

PrimeNG version

17..

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

20.8.1

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

@adri95cadiz adri95cadiz 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 7, 2024
@mehmetcetin01140
Copy link
Contributor

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 open a new issue so we can include it in our roadmap?

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

2 participants