Password. When disabled, you can tab to it and type value anyway.

[iskalyakin]

I'm submitting a ... (check one with "x")

[x ] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35

Plunkr Case (Bug Reports)
Please demonstrate your case at stackblitz by using the issue template below. Issues without a test case have much less possibility to be reviewd in detail and assisted.

https://stackblitz.com/edit/stackblitz-starters-qdqnih2f

Current behavior
Make password field disabled. After it component doesn't react on click, but can be focused and edited by tab.

Expected behavior
Disabled password component shouldn't be accessable either by click or tab.

Minimal reproduction of the problem with instructions
Minimal demo: https://stackblitz.com/edit/stackblitz-starters-qdqnih2f
Steps:

1. Make password field disabled.
2. Tab to it. You can, and it seems like an issue.

What is the motivation / use case for changing the behavior?
Current behavior can lead to forms filling issues for users.

Please tell us about your environment:
ubuntu 18.04, yarn.

• Angular version: 5.X
  18.0.1

• PrimeNG version: 5.X
  18.0.1

• Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
  all

• Language: [all | TypeScript X.X | ES6/7 | ES5]
  all

• Node (for AoT issues): node --version =
  all

[mertsincan]

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,

[iskalyakin]

Hi. Thank you for the answer. Unfortunatly, it looks like this problem is still here, at least in 13 version (which is used for password component example).
https://stackblitz.com/edit/primeng-password-demo-kaqf6r?file=src%2Fapp%2Fapp.component.html

[mehmetcetin01140]

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,

[iskalyakin]

Hi! Unfortunately, the issue is still here: https://stackblitz.com/edit/stackblitz-starters-qdqnih2f

[mertsincan]

Thanks a lot, @iskalyakin ! Could you please update issue template? version, sample link vs.
I'll set the correct milestone to this issue asap.

[iskalyakin]

ok, updated.

[github-actions]

We're unable to replicate your issue. Could you please try it with the latest PrimeNG version? If the problem continues, could you create a reproducer using PrimeNG Issue Template or provide additional details by editing this issue? This issue will be closed if no activities in 20 days.