Closed Bug 1722305 Opened 10 months ago Closed 7 months ago

will-navigate doesn't fire and previous target isn't destroyed when navigating away from a bfcached *and* paused page

Categories

(DevTools :: Framework, defect)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ochameau, Unassigned)

References

Details

(Whiteboard: dt-fission-future, dt-perf-stability-mvp)

When navigating away from a page that is paused and we are navigating to a page that was stored in the bfcache, we at least miss:

STR:

  • Open a tab
  • Load data:text/html,<script>debugger;</script>
  • Navigate to data:text/html,foo
  • Navigate back to data:text/html,<script>debugger;</script> (using back button)
  • Open the debugger
  • Reload the page
    => The debugger will pause on the debuggger statement
  • Navigate to the second page (using forward button)
    => The debugger will still report to be paused on the previous page, while we loaded the second
    => The debugger should have been resumed. It isn't because we miss will-navigate. The miss of target-destroyed event isn't so important because we do get the notification of the new target of the second page. And the TargetCommand will report all previous target as being destroyed:
    https://searchfox.org/mozilla-central/rev/59e797b66f5ce8a27ede0e7677688931be7aed20/devtools/shared/commands/target/target-command.js#168-174
Whiteboard: dt-fission-m3-triage → dt-fission-future
Whiteboard: dt-fission-future → dt-fission-future, dt-perf-stability-triage
See Also: → 1720443
Whiteboard: dt-fission-future, dt-perf-stability-triage → dt-fission-future, dt-perf-stability-mvp

Tested again and has been fixed!

Status: NEW → RESOLVED
Closed: 7 months ago
Resolution: --- → FIXED
See Also: → 1738941
You need to log in before you can comment on or make changes to this bug.