Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

content: document alternative to dismissOnPageChange (ionNavWillChange, ionNavDidChange)

Open
#846 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
angular
Domain
documentation

Research direction

Start with BREAKING_ARCHIVE/v4.md at the overlays section and review the existing dismissOnPageChange workaround. Check the Angular router-events usage shown in the issue, especially NavigationEnd, and document a usable alternative with enough context for readers to apply it. Done means the page no longer points to an undocumented event without explaining how to use the recommended approach.

Written by the indexing model from the issue text.

Description

content

URL
https://github.com/ionic-team/ionic-framework/blob/main/BREAKING_ARCHIVE/v4.md#overlays

What is missing or inaccurate about the content on this page?
The doc says that as a workaround for the removed dismissOnPageChange, there are global events (ionNavWillChange, ionNavDidChange) that you can listen to in order to detect when navigation occurs.

I can't find any documentation anywhere on how to actually use ionNavDidChange, so this is not a great proposed alternative.

I managed to get it working using this code in app.component.ts to subscribe to Angular router events:

router.events.subscribe(event => {
  if (event instanceof NavigationEnd) {
    // Do something
  }
});

Perhaps this should be documented as an alternative to dismissOnPageChange.

Dominant language
MDX
Stars
621
Forks
3.2k
Avg merge
1d 2h
Merged PRs (30d)
86

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ionic-team/ionic-docs

All issues in ionic-team/ionic-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.