SafariViewController is way too cumbersome to dismiss

Originator:raylillywhite
Number:rdar://22963376 Date Originated:2015-10-03
Status:Duplicate of 21524363 (Open) Resolved:
Product:iOS Product Version:iOS 9.1 beta 3
Classification:UI/Usability Reproducible:Always
 
Summary:
SafariViewController has many huge advantages to UX (shared cookies, disappearing top bar, reader mode), but it's so hard to navigate away from that I'd actually rather every app switch directly to Safari. If an app switches to Safari, I can 3D Touch swipe to return to the app or tap on the status bar back button. But if an app uses SafariViewController, I have to pull down on the content to reveal the top bar (and not too slow, or the bar won't come down), then adjust the grip on my phone so that I can reach the top corner to press the done button. A simple solution (simple in terms of design, a little bit harder in terms of engineering), would be to make the interactive back gesture in SafariViewController dismiss the view controller if you're already at the first page.

Steps to Reproduce:
1. Read content in a SafariViewController modal
2. Try to go back

Expected Results:
It's a single gesture to go back

Actual Results:
You have to scroll down quickly then tap a button in the hard-to-reach top part of the screen.

Version:
iOS 9.1 beta 3

Notes:


Configuration:
iPhone 6S

Attachments:

Comments

iOS 9.2 Beta 2 notes indicate that this is fixed:

Safari View Controller can now be dismissed using an edge swipe. You must rebuild your app against the iOS 9.2 SDK or later in order to take advantage of this new behavior.

By raylillywhite at Nov. 3, 2015, 8:53 p.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!