Skip to content

Root RadSideDrawer + ActionBar save area issue with NativeScript 4.x.x on iOS  #5672

Closed

Description

@NickIliev

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.

Steps to reproduce:

  • use this applicaiton on iOS device/emulator.
  • the RadSideDrawer is placed as root in app.component.html
  • the first loaded page is without ActionBar
  • when navigating to a page with ActionBar like 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.

Activity

  1. removed their assignment
    on May 29, 2018
  2. chrisse27 commented on May 29, 2018

    @chrisse27

    @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.

  3. ghost removed on Jun 1, 2018
  4. MartoYankov commented on Jun 1, 2018

    @MartoYankov
    Contributor

    @chrisse27 We found a way to work around the issue and will release a patch version for the nativescript-ui-sidedrawer today.

  5. chrisse27 commented on Jun 1, 2018

    @chrisse27

    Cool, thanks for the update.

  6. MartoYankov commented on Jun 1, 2018

    @MartoYankov
    Contributor

    @chrisse27 We have released the patch version 4.1.1. Can you check it out?

  7. chrisse27 commented on Jun 1, 2018

    @chrisse27

    @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

      <StackLayout tkDrawerContent style="margin-top: -safeAreaInsetTop">
        ...
      </StackLayout>
    

    where safeAreaInsetTop is set in our source code.

  8. MartoYankov commented on Jun 1, 2018

    @MartoYankov
    Contributor

    @chrisse27 Yep, we are aware that this is problematic and providing ways to handle the safe area on iOS 11 is on our roadmap.

  9. lock commented on Aug 26, 2019

    @lock

    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.

  10. locked and limited conversation to collaborators on Aug 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions