1612538 - Move all page navigation related code into parent process

Status: RESOLVED WONTFIX

(Remote Protocol :: CDP, task, P3)

Description

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Before the work on the JSWindowActor API can be started, all the page navigation related code should be moved out of the content processes. That was a clear statement by the Fission team when I was talking with them about Fission during the office hours.

So this affects pure navigation, reload, and back and forward navigation.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+1]]

When working on this bug we have to make sure to add a certain amount of navigation tests before doing the refactoring.

Comment 3

[Maja Frydrychowicz :impossibus (was :maja_zf) (needinfo me)]

For Page.navigate, for example, calling this.session.browsingContext.loadURI from the parent Page domain seems to work. Does that fulfill the goal of moving out of the content process? (If yes, then moving navigate at least is trivial)

Try push: https://treeherder.mozilla.org/#/jobs?repo=try&revision=066f260d2b305bf5685060901a623837cba58e31

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

No, we still register listeners for all the required events (DOMContentLoaded, load, etc) in the content process. We have to get everything moved into the parent process. Same also applies to history navigation.

Comment 5

[Chris Peterson [:cpeterson]]

Tracking for Fission M6b Nightly milestone.

Comment 6

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Our current code around navigation works just fine with Fission enabled. The only issue that we currently have is with COOP involved (bug 1706353).

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+1]]

We don't have the time to get this refactoring done. Instead one should use the WebDriver BiDi protocol.