SafariView Improvements #74
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Once again, this is a rewrite of the SafariView. This, however, will make the NavigationView push the Safari controller instead of using a sheet (but the latter is still an option). This creates a better UX, as it follows how Safari controllers are presented in other iOS apps. This change does not require changes in pre-existing uses of
.safariView(), as it is done all under the hood. (However, because pushing in the Navigation stack does fix the collapsing bar issue (at least on SwiftUI previews?), the SafariView.Configuration used in SettingsAboutView has been modified accordingly).TL;DR: new default presentation mode for
.safariView()because the implementation is re-written(god please let this be the last time i have to do this pr)