-
Notifications
You must be signed in to change notification settings - Fork 13.5k
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
bug: disabled select inside item is not being fully disabled #29234
bug: disabled select inside item is not being fully disabled #29234
Comments
Thank you for the issue. The main issue is that I can at least confirm that this is specific to Angular Standalone, and does not occur in React or Vue. |
Hello @Airdevelopments, I'm having issues reviewing the reproduction link provided. It does not want to load in Chrome. Would you be kind enough to submit a github repository or double check the link provided and see if you can provided a forked version of the Stackbliz template (not just the preview link). Thank you! |
@sean-perkins |
@Airdevelopments really appreciate the timely update on the reproduction! Here's a dev-build to test with:
Forked reproduction with dev-build: https://stackblitz.com/edit/angular-vvbkmf-zrcmlc Let me know if you experience any issues! |
Issue number: resolves #29234 --------- <!-- Please do not submit updates to dependencies unless it fixes an issue. --> <!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. --> ## What is the current behavior? <!-- Please describe the current behavior that you are modifying. --> In certain scenarios, such as in Angular where the property binding is set a few frames after the element is rendered, the `ionStyle` event from `ion-select` can be emitted before `ion-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? <!-- Please describe the behavior or changes that are being added by this PR. --> - Emits the `ionStyle` event when the `ion-select` is rendered. - `ion-item` consistently detects the state of `ion-select` and applies the appropriate styles ## Does this introduce a breaking change? - [ ] Yes - [x] No <!-- If this introduces a breaking change: 1. Describe the impact and migration path for existing applications below. 2. Update the BREAKING.md file with the breaking change. 3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/docs/CONTRIBUTING.md#footer for more information. --> ## Other information <!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. --> Forked reproduction and dev-build available here: #29234 (comment)
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out. |
Prerequisites
Ionic Framework Version
v7.x
Current Behavior
Note: The issue only seems to appear when using Angular standalone components
When disabling a
<ion-select>
inside of a<ion-item>
, the hover and touch / click styling still appears as enabled and pointer events are still executed.Expected Behavior
We would expect the styling to appear disabled as well as
point-events: none
causing no(click)
handlers to be called. This does seem to be the case when using the classicIonicModule.forRoot()
approach and non-standalone components.Steps to Reproduce
Code Reproduction URL
https://stackblitz.com/edit/angular-vvbkmf-cz7bqx?file=src%2Fapp%2Fapp.component.html
Ionic Info
see Stackblitz setup
Additional Information
No response
The text was updated successfully, but these errors were encountered: