AP.history.popState does not trigger for Custom Content list view component

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • Component/s: Ecosystem
    • None
    • Severity 3 - Minor

      Issue Summary

      When a user navigates from some existing browser history state to initial (by clicking an app link in the navigation panel) `AP.history.popState` doesn't trigger

      Steps to Reproduce

      1. Prepare an app with the Custom Content module:
        • register a type on a space level (`supportedContainerTypes: ['space']`)
        • add listViewComponent property and refer to `generalPages` module
      2. Implement `generalPage` module
        • add usage of `AP.history` module
        • add a new state to history with `AP.history.pushState("page1");`
        • add a listener when a state is changed with `AP.history.popState`
      3. Install the app on some instance. The link should appear on the navigation panel
      4. Click on a link on the navigation panel
      5. Ensure that a state is changed to "page1" (the url should contain `#!page1` location hash)
      6. Click on a link on the navigation panel again

      Expected Results

      `AP.history.popState` should be invoked

       

      Actual Results

      History is updated, `AP.history.popState` is not invoked

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            Oleksandr Beztsinnyi
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: