Closed Bug 1809290 Opened 2 years ago Closed 2 years ago

Add wdspec tests for BiDi network events subscribed for a single context

Categories

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

task
Points:
1

Tracking

(firefox110 fixed)

RESOLVED FIXED
110 Branch
Tracking Status
firefox110 --- fixed

People

(Reporter: jdescottes, Assigned: jdescottes)

References

(Blocks 1 open bug)

Details

(Whiteboard: [webdriver:m5], [wptsync upstream])

Attachments

(1 file)

With the initial implementation of the 3 first network events (network.beforeRequestSent, network.responseStarted, network.responseCompleted), all wdspec tests are only checking subscriptions to all contexts.

Since this event is handled from the parent process it's important to check that when monitoring events for a given browsing context, you don't receive events from other contexts.

Assignee: nobody → jdescottes
Status: NEW → ASSIGNED

(In reply to Julian Descottes [:jdescottes] from comment #0)

Since this event is handled from the parent process it's important to check that when monitoring events for a given browsing context, you don't receive events from other contexts.

Given that in our implementation we got it implemented in the parent process we cannot assume the same for Chrome or other browsers. At the same time other browsers also could have eg. navigation events implemented via the parent process. As such we might have to add such a test for all the events that we currently support. Happy to file a new bug and to discuss in next week's triage meeting if we agree.

(In reply to Henrik Skupin (:whimboo) [⌚️UTC+1] from comment #2)

(In reply to Julian Descottes [:jdescottes] from comment #0)

Since this event is handled from the parent process it's important to check that when monitoring events for a given browsing context, you don't receive events from other contexts.

Given that in our implementation we got it implemented in the parent process we cannot assume the same for Chrome or other browsers. At the same time other browsers also could have eg. navigation events implemented via the parent process. As such we might have to add such a test for all the events that we currently support. Happy to file a new bug and to discuss in next week's triage meeting if we agree.

Right I just remembered Sasha filed a general bug 1802537

Blocks: 1802537
Points: --- → 1
Priority: -- → P1
Whiteboard: [webdriver:m5]
Pushed by jdescottes@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a36380efa4c8 [wdspec] Add BiDi network event tests subscribing to a single context r=webdriver-reviewers,whimboo
Failed to create upstream wpt PR due to merge conflicts. This requires fixup from a wpt sync admin.
Whiteboard: [webdriver:m5] → [webdriver:m5], [wptsync upstream error]
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 110 Branch
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/37932 for changes under testing/web-platform/tests
Whiteboard: [webdriver:m5], [wptsync upstream error] → [webdriver:m5], [wptsync upstream]
Upstream PR merged by moz-wptsync-bot
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: