Skip to content

Nested frames (fragments) disappear when their parent frame (fragment) is animated #6659

Closed as not planned

Description

@manoldonev

Environment

  • CLI: 5.0.2
  • Cross-platform modules: 5.0.5
  • Android Runtime: 5.0.0

Describe the bug
Nested frames (i.e. fragments) disappear when their parent is animated. Related to #6641 but the problem is not specific to TabView and is more general. Caused by https://issuetracker.google.com/issues/36970570 -- arcane issue that Google somehow marked as obsolete & won't fix.

To Reproduce
Tap "navigate to some page" -- notice how the "Players" part of the page disappears immediately instead of transitioning away with the rest of the view.

Sample project
Playground project for reference: https://play.nativescript.org/?template=play-tsc&id=BZfk8A&v=5


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Activity

  1. self-assigned this
    on Dec 4, 2018
  2. changed the title [-]Nested frames (fragments) disappear when their parent is animated[/-] [+]Nested frames (fragments) disappear when their parent frame (fragment) is animated[/+] on Dec 4, 2018
  3. ghost removed on Dec 12, 2018
  4. manoldonev commented on Mar 8, 2019

    @manoldonev
    ContributorAuthor

    Reopening this issue as it could occur in a similar scenario but when navigating backwards from a nested-frame page.

    To reproduce:

    1. Define a frame root for your app (default page contains no frames i.e. we have single frame scenario)
    2. Navigate to a different page that contains additional frame (i.e. we now are in a nested frame scenario)
    3. Navigate back with android hardware button -- nested frame/fragment disappears immediately.

    Sample Project:
    Archive.zip

    Note this problem can only be observed after #7011 is merged

  5. added this to the 5.3 milestone on Mar 8, 2019
  6. modified the milestones: 5.3, 5.4 on Apr 3, 2019
  7. removed their assignment
    on Nov 23, 2019
  8. farfromrefug commented on May 5, 2020

    @farfromrefug
    Collaborator

    The fix you implemented where you dispose the current fragment on onUnloaded has bad consequences for apps with map for example.
    Doing so create unecessary OpenGL redrawing (becuase the mapview is recreated on every pause/resume).

    PLus running the sample app i actually cant see any issue as explaned here.
    I will create a PR to remove that behavior fix. Hoping for you guys to accept it.

  9. NathanWalker commented on Oct 23, 2026

    @NathanWalker
    Contributor

    Closing in favor of #7772, which tracks the overhaul of Android page navigation transitions, including nested fragments that disappear while their parent animates. Several partial fixes have landed since (#6677, #8793). Please add current repros there.

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

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions