Closed Bug 1810357 Opened 3 years ago Closed 3 years ago

Add HTTP target routes

Categories

(Remote Protocol :: CDP, enhancement, P5)

Firefox 110
enhancement

Tracking

(firefox116 fixed)

RESOLVED FIXED
116 Branch
Tracking Status
firefox116 --- fixed

People

(Reporter: canadahonk, Assigned: canadahonk)

References

Details

Attachments

(1 file)

Steps to reproduce:

Add HTTP target routes like /json/new into the CDP implementation. Relevant CDP docs: https://chromedevtools.github.io/devtools-protocol/#get-jsonnewurl

(Happy to work on this myself.)

Actual results:

Currently they just return 404s as they aren't implemented.

Expected results:

Handle the requests to the target routes instead of 404.

Added support for /json/new, /json/activate/{targetId},
/json/close/{targetId}. Rewrote JSONHandler internals to support
different routes by HTTP method, and prefixed routes which are required
by activate and close due to inlining the targetId into the request url.

This is a work-in-progress as tests are yet to be added, and it might be
better to depend upon already open D166873 to avoid merge conflicts.
Passes linting but looking for code feedback, apologies for any troubles
by major internal changes.

Assignee: nobody → oj
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Severity: -- → S3
Priority: -- → P5
Attachment #9312377 - Attachment description: WIP: Bug 1810357 - [cdp] Add HTTP target routes → Bug 1810357 - [cdp] Add HTTP target routes
Pushed by oj@oojmed.com: https://hg.mozilla.org/integration/autoland/rev/d125ec07af0b [cdp] Add HTTP target routes r=webdriver-reviewers,whimboo
Regressions: 1838833
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 116 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: