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-inputNumber: onInputBlur NPE #14928

Closed
DbkMG opened this issue Mar 1, 2024 · 5 comments
Closed

p-inputNumber: onInputBlur NPE #14928

DbkMG opened this issue Mar 1, 2024 · 5 comments
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working

Comments

@DbkMG
Copy link

DbkMG commented Mar 1, 2024

Describe the bug

p-inputNumber onInputBlur-Method throws NPE if value==null

Environment

chrome browser

Reproducer

No response

Angular version

17.2.3

PrimeNG version

17.9.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.13.0

Browser(s)

No response

Steps to reproduce the behavior

Reproducable in primeng showcase

  1. go to https://primeng.org/inputnumber
  2. scroll down to Float Label Example
  3. focus inputfield
  4. blur
  5. check webdev-console

Expected behavior

No NPE

@DbkMG DbkMG 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 1, 2024
@adcore-dev
Copy link

The problem here that model after blur become string. It wasn't happen before

@vigalo
Copy link
Contributor

vigalo commented Mar 2, 2024

As @adcore-dev said, the model becomes string. This problem broken my app and made me downgrade to 17.8.0 until fixed

@mehmetcetin01140 mehmetcetin01140 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 Mar 4, 2024
@psarno
Copy link

psarno commented Mar 4, 2024

I just came here to report this same thing, I couldn't find a suitable workaround.

I'm going to have to downgrade also. It seems there is a brand new PR for it though.

@rosenthalj
Copy link
Contributor

PR #15015 fixes this issue and issue #15014 and issue #15017

@cetincakiroglu
Copy link
Contributor

Hi,

Thanks for reporting the issue, this issue has been fixed by @rosenthalj in 9b0518e

This issue is superseded by #15014

Closing the issue.

@cetincakiroglu cetincakiroglu removed this from the 17.11.0 milestone Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants