fix(picker-column): fallback to elementFromPoint for iOS 16 Shadow DOM bug #30479
+21
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…M bug Co-authored-by: Vilhelm Josander <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ShaneK
approved these changes
Jun 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #29672
What is the current behavior?
The issue on iOS 16 with
elementsFromPointis related to how it handles Shadow DOM retargeting when called from the document (global) context.It leads to an
undefinedelement that is required to triggerionChange.What is the new behavior?
'ion-picker-column-option'.Does this introduce a breaking change?
Other information
Dev build:
8.6.2-dev.11749761258.1b46b6a9