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 }}
Repository navigation
Root RadSideDrawer + ActionBar save area issue with NativeScript 4.x.x on iOS #5672
Using nativescript-ui-sidedrawer@4.0.0 with tns-core-modules@4.0.0 is causing save area movement issue for the RadSideDrawer when used with pages with and without ActionBar.
when navigating to a page with ActionBarlike this one (tap "Home" or some login option) the RadSideDrawer is "jumping" and starts showing up behind the save area - best visualized on iPhoneX but reproducible on each iOS 11 device.
@NickIliev Would it be possible to have a look at the side drawer source code, so we could figure out what's going wrong in this case. This issue is currently blocking as from releasing a new version of an app for our customer.
@MartoYankov Behavior is now consistent for pages with and without ActionBars. So I would consider this issue fixed. To make the side drawer draw itself up to the very top on iPhoneX I added a negative margin to tkDrawerContent
Activity
chrisse27 commentedon May 29, 2018
@NickIliev Would it be possible to have a look at the side drawer source code, so we could figure out what's going wrong in this case. This issue is currently blocking as from releasing a new version of an app for our customer.
MartoYankov commentedon Jun 1, 2018
@chrisse27 We found a way to work around the issue and will release a patch version for the nativescript-ui-sidedrawer today.
chrisse27 commentedon Jun 1, 2018
Cool, thanks for the update.
MartoYankov commentedon Jun 1, 2018
@chrisse27 We have released the patch version 4.1.1. Can you check it out?
chrisse27 commentedon Jun 1, 2018
@MartoYankov Behavior is now consistent for pages with and without ActionBars. So I would consider this issue fixed. To make the side drawer draw itself up to the very top on iPhoneX I added a negative margin to tkDrawerContent
where safeAreaInsetTop is set in our source code.
MartoYankov commentedon Jun 1, 2018
@chrisse27 Yep, we are aware that this is problematic and providing ways to handle the safe area on iOS 11 is on our roadmap.
lock commentedon Aug 26, 2019
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.