5cecd97493
NgModel internally coerces any arbitrary value that will assigned to the `disabled` `@Input` to a boolean. This has been done to support the common case where developers set the disabled attribute without a value. For example: ```html <input type="checkbox" [(ngModel)]="value" disabled> ``` This worked in View Engine without any errors because inputs were not strictly checked. In Ivy though, developers can opt-in into strict template type checking where the attribute would be flagged. This is because the `NgModel#isDisabled` property type-wise only accepts a `boolean`. To ensure that the common pattern described above can still be used, and to reflect the actual runtime behavior, we should add an acceptance member that makes it work without type checking errors. Using a coercion member means that this is not a breaking change. PR Close #34438
Angular
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages.
Quickstart
Changelog
Learn about the latest improvements.
Want to help?
Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our guidelines for contributing and then check out one of our issues in the hotlist: community-help.