fix(angular): persist select disabled state in item #29448
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue number: resolves #29234
What is the current behavior?
In certain scenarios, such as in Angular where the property binding is set a few frames after the element is rendered, the
ionStyle
event fromion-select
can be emitted beforeion-item
has registered an event listener.This results in situations like setting the
ion-select
as initially disabled can cause the item to not treat the element as not interactable (receives pointer events).What is the new behavior?
ionStyle
event when theion-select
is rendered.ion-item
consistently detects the state ofion-select
and applies the appropriate stylesDoes this introduce a breaking change?
Other information
Forked reproduction and dev-build available here: #29234 (comment)