1841010 - Create a helper to track navigations and retrieve the current navigation id for a context

Status: RESOLVED FIXED

(Remote Protocol :: WebDriver BiDi, task, P2)

Description

[Julian Descottes [:jdescottes]]

As a prerequisite to return navigation ids in various commands and events, we should create a helper/utility that will be able to track navigation for all contexts, and return the current navigation id for any context.

Tracking the navigations might be handled in the parent or content processes, however the service itself should be available in the parent process:

• need to access the unique context ids which are only available in the parent for now
• network events (which need a navigation id when relevant) are handled in the parent process

Comment 1

[Julian Descottes [:jdescottes]]

Bug 1835704 will be relevant here, but we will most likely move forward with an implementation based on the current callbacks available in the WebProgressListener. So not blocking on it, just see also.

Comment 2

[Julian Descottes [:jdescottes]]

Attachment: Bug 1841010 - [remote] Add a NavigationManager to monitor navigations using JSWindowActors

Comment 3

[Julian Descottes [:jdescottes]]

Attachment: Bug 1841010 - [remote] Start monitoring navigations on WebDriver session startup

Depends on D180440

Comment 4

[Julian Descottes [:jdescottes]]

Attachment: Bug 1841010 - [remote] Expose a NavigationManager instance on the RootMessageHandler

Depends on D180440

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/dbe6eebd6aff
[remote] Add a NavigationManager to monitor navigations using JSWindowActors r=webdriver-reviewers,Sasha
https://hg.mozilla.org/integration/autoland/rev/8efc6ba50695
[remote] Expose a NavigationManager instance on the RootMessageHandler r=webdriver-reviewers,jgraham

Comment 6

[Iulian Moraru]

https://hg.mozilla.org/mozilla-central/rev/dbe6eebd6aff
https://hg.mozilla.org/mozilla-central/rev/8efc6ba50695