Open Bug 1878860 Opened 1 year ago Updated 11 months ago

Cross-origin iframes not always loaded after navigate with wait=complete

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

(Blocks 1 open bug)

Details

(Whiteboard: [webdriver:backlog])

While working on Bug 1874920, we updated the test at https://searchfox.org/mozilla-central/rev/896042a1a71066254ceb5291f016ca3dbca21cb7/testing/web-platform/tests/webdriver/tests/bidi/browsing_context/get_tree/frames.py#94 to use cross origin frames.

The test page contains two iframes loaded on another domain. We use a browsingContext.navigate with wait=complete. However the test was intermittently failing, sometimes one of the iframes was not fully loaded and did not have its final URL yet.

As a workaround we are waiting for load events on top of waiting for navigate to resolve, but in theory this should not be necessary?

Blocks: 1730641
Summary: Cross origine iframes not always loaded after navigate with wait=complete → Cross-origin iframes not always loaded after navigate with wait=complete

I wonder if this actually applies to all the navigation commands including reload, and navigating back and forward.

Write a test

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