This repository has been archived by the owner on Jan 26, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 17
22106545: automaticallyAdjustsScrollViewInsets doesn't change insets on iOS 9 #11
Labels
Milestone
Comments
This was referenced Aug 3, 2015
19796494: SIGSEGV - segmentation violation - [UITextSelectionView textSelectionViewActivated:]
#2031
Open
Open
This was referenced Aug 10, 2015
19006288: SIGSEGV - segmentation violation - [UITextSelectionView textSelectionViewActivated:]
#2708
Open
Open
This was referenced Apr 14, 2016
Open
Open
This was referenced Jun 23, 2016
Open
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Summary:
On iOS 8, it was possible to layout a UITableView in code so that it would fill the screen, including under a UINavigatonBar. Unless you set the automaticallyAdjustsScrollViewInsets property of the UIViewController otherwise, the insets on the tableview were changed so that content would not appear below the navigation bar until the tableview was scrolled up.
In iOS 9, that functionality still appears to work when using storyboards, but it no longer works when adding the table view as a subview and applying constraints to it in code.
Steps to Reproduce:
Expected Results:
I would expect the behavior to be the same on both iOS 8 and iOS 9
Actual Results:
On iOS 9, the content in the tableview are not offset by the height of the navigation bar.
Version:
iOS 9.0 (13A4305g)
Notes:
I left a second storyboard with the TableView laid out there so it is easy to see that it works on iOS 9.
Configuration:
iPod touch, 5th generation running iOS 9; verified correct behavior on an iPhone 5s running iOS 8.4
Attachments:
'TableViewTest.zip', 'iOS 8.4 - visible content.png' and 'iOS 9.0 beta 4 - content hidden.png' were successfully uploaded.
Product Version: iOS 9 beta 4
Created: 2015-08-02 03:32:35.060200
Originated: 2015-08-01T00:00:00
Open Radar Link: http://www.openradar.me/22106545
The text was updated successfully, but these errors were encountered: