Closed Bug 2041335 Opened 3 months ago Closed 1 month ago

Stop using enterNestedEventLoop in webdriver bidi debugging module

Categories

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

task

Tracking

(firefox155 fixed)

RESOLVED FIXED
155 Branch
Tracking Status
firefox155 --- fixed

People

(Reporter: jdescottes, Assigned: khalid.alhaddad98)

References

Details

(Whiteboard: [webdriver:m21][webdriver:external][webdriver:relnote])

Attachments

(1 file)

See https://phabricator.services.mozilla.com/D288831?id=1263891#inline-1617357

At the moment the WebDriver BiDi debugging module uses the same API as devtools to enter a nested event loop enterNestedEventLoop. This might create conflicts with DevTools if used in parallel with BiDi.

Instead we can emulate a similar behavior via

this.#paused = true;
Services.tm.spinEventLoopUntil("webdriver-bidi-debugging", function () {
    return !this.#paused;
});
Priority: -- → P3
Whiteboard: [webdriver:backlog]
Assignee: nobody → khalid.alhaddad98
Depends on: 2060460
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 155 Branch
Whiteboard: [webdriver:backlog] → [webdriver:m21][webdriver:external]
Whiteboard: [webdriver:m21][webdriver:external] → [webdriver:m21][webdriver:external][webdriver:relnote]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: