While running through the resolutions to test some changes to support the new safe area insets features, I noticed that the "top" seems incorrect in the simulator for the iPad devices. From what I understood, none of the original iPads (represented in the simulator) have any insets we need to be concerned with and it should really only affect the iPhone X type of displays in the simulator right now (and maybe some TV devices). However, after updating to use the new insets, I noticed problems with some simulator configs.
My app is configured for landscape mode, and most configs work fine, but a few aren't rendering correctly in the simulator because of this behavior. I captured raw values to help understand what was going on.
If I use the iPad Mini (768x1024):
>>>>> Raw Insets (t,l,b,r): 18.75,0,0,0
If I use the borderless equivalent of iPad @ 1x (768x1024):
>>>>> Raw Insets (t,l,b,r): 9.375,0,0,0
If I use iPhone X (1125x2436) the values appear to be correct for landscape mode:
>>>>> Raw Insets (t,l,b,r): 0,37.546669006348,17.920000076294,37.546669006348
I see that I could just change the values in the skins definitions myself, but I just want to double check to make sure I'm not overlooking something. I don't believe there is a permanent status bar or unusable area on those devices.
Also, the config for the iPads looks different than what I'm seeing in iPhone X, so I'm thinking some of the simulator configs may have been overlooked when this feature was introduced? In particular, some just seem to use safeLandscapeScreenInsetStatusBar whereas the new ones for iPhone X seem to be more complete (as I was expecting to see: safeLandscapeScreenInsetTop, etc).