For iOS 11 use safeAreaInsets rather than topLayout #78
Conversation
This file contains 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
|
@magister-ludi-x Did you observe any issues? Otherwise I would have expected the topLayoutGuide to fallback to the safeAreaInset. Could you provide an example of where this makes a difference? Ideally add this as a comment in code. |
|
In my app the invocation of "self.topLayoutGuide.length" itself in maximumAvailableHeightWithSize causes UIViewAlertForUnsatisfiableConstraints, while "self.view.safeAreaInsets.top" works fine. I'm running under Xcode 10 beta 4 though, haven't tried under Xcode 9. I'll try to extract a repro, time permitting. |
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.
No description provided.