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-autoComplete: Input field remains disabled if using the disabled attribute #191

Closed
cghislai opened this issue Apr 12, 2016 · 3 comments
Closed
Assignees
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@cghislai
Copy link

When using the autoComplete component with [disabled]="myControllerBooleanValue", the input remains disabled event when myControllerBooleanValue evaluates to false.

The disabled="false" attribute is set on the input element, but it seems that browsers only check the presence of this attribute rather than its value. The ui-state-disabled class is present as well.

@cghislai cghislai changed the title p-autoComplete: Input field remains disbabled if using the disabled attribute p-autoComplete: Input field remains disabled if using the disabled attribute Apr 12, 2016
@cghislai
Copy link
Author

If the dropdown button is present, it remains active

@cagataycivici cagataycivici added the Type: Bug Issue contains a bug related to a specific component. Something about the component is not working label Apr 13, 2016
@cagataycivici cagataycivici added this to the 1.0.0-beta.2 milestone Apr 13, 2016
@cagataycivici cagataycivici self-assigned this Apr 13, 2016
@irapopova
Copy link

Is this fixed ?
I'm using primeng": "~2.0.1" and it still has this issue

@Neonell
Copy link

Neonell commented Feb 27, 2018

As workaround I'm setting a boolean attribute in the ngOnInit method based on the input parameter value. This is working and if the boolean attribute is set to false then the element is enabled. (so false if undefined or false and true if set to true). I cannot explain why it is working only with normal attribute and not with @input attributes... I also was surprised by this behavior as Typescript is type-safe.

atretyak1985 pushed a commit to Nanitor/primeng that referenced this issue Jul 18, 2020
Overview: Error when user or weakest_link is null
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

No branches or pull requests

4 participants