fix for iOS 16 - force safeAreaInsets update #53
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.
Checklist
Description
isHidden
to false on aUIWindow
triggers an update to thesafeAreaInsets
on the view of the window'srootViewController
. In iOS 16 (and the 17 beta), this update was not happening. So calculatingadditionalSafeAreaInsets
was happening withsafeAreaInsets == .zero
instead of the correct value.Related Issue
N/A
Motivation and Context
There were issues with layout of AccessibilitySnapshot. This led to a detailed investigation of the root cause and this pull request.
Screenshots
Screenshots of debugging the calculation of
additionalSafeAreaInsets
inSnapshotWindow.swift
iOS 15
--
iOS 16