You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
In iOS 11.0, UIViewController.automaticallyAdjustsScrollViewInsets is deprecated in favor of UIScrollView.contentInsetAdjustmentBehavior. automaticallyAdjustsScrollViewInsets has always been a bit of a pain for us, versus how macOS handles the same configuration option, because it’s a property on the containing view controller instead of the view itself. (We have to crawl up the responder chain looking for the view controller just to update MGLMapView’s internal constraints.) MGLMapView should implement its own contentInsetAdjustmentBehavior property that lets the developer indicate whether the MGLMapView itself should adjust the insets automatically.
We’ll have to keep support for UIViewController.automaticallyAdjustsScrollViewInsets around until that property is removed from the (Apple) iOS SDK, in case any developer depends on the currently documented behavior.
In iOS 11.0,
UIViewController.automaticallyAdjustsScrollViewInsets
is deprecated in favor ofUIScrollView.contentInsetAdjustmentBehavior
.automaticallyAdjustsScrollViewInsets
has always been a bit of a pain for us, versus how macOS handles the same configuration option, because it’s a property on the containing view controller instead of the view itself. (We have to crawl up the responder chain looking for the view controller just to update MGLMapView’s internal constraints.) MGLMapView should implement its owncontentInsetAdjustmentBehavior
property that lets the developer indicate whether the MGLMapView itself should adjust the insets automatically.We’ll have to keep support for
UIViewController.automaticallyAdjustsScrollViewInsets
around until that property is removed from the (Apple) iOS SDK, in case any developer depends on the currently documented behavior./ref #12142 #10485
/cc @friedbunny @julianrex
The text was updated successfully, but these errors were encountered: