Fire Navigating/Appearing/Disappearing for a popped page prior to the page get disconnected
Open
area-core-lifecycle
Task
- Dominant language
- C#
- Stars
- 23.3k
- Forks
- 2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 290
Description
Currently these LC events all fire after a page has been unparented which means properties like the Window are null. We should mostly likely fire `Navigating/Appearing/Disappearing` before any changes have actually been applied.
Contributor guide
Research direction
No files or tests are named. Start by tracing the lifecycle handling for Navigating, Appearing, and Disappearing when a page is popped, then reproduce the unparenting sequence; done means these events fire before disconnection so properties such as Window remain available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100