Open Bug 1859249 Opened 2 years ago Updated 1 year ago

NavigationManager should check the URL before skipping navigation-started events

Categories

(Remote Protocol :: WebDriver BiDi, defect, P3)

Product:
Remote Protocol
Component:
WebDriver BiDi
Type:
defect
Points:
2

Tracking

(Not tracked)

People

(Reporter: jdescottes, Unassigned)

References

Details

(Whiteboard: [webdriver:backlog])

See reasoning in Bug 1858034 comment 2, this could help in scenarios where we receive events from old browsing contexts out of order during a process change.

if we receive a navigation-started event for a navigable which already has a navigation tracked but for a different URL, we should assume this is a new navigation.

There might be an issue with redirects if we implement the workaround suggested above. Need to check if we have tests for this.

Severity: -- → S3
Points: --- → 2
Priority: -- → P3
Whiteboard: [webdriver:backlog]
Depends on: 1859299
You need to log in before you can comment on or make changes to this bug.