Open
Bug 1391465
Opened 8 years ago
Updated 2 years ago
Implement a skeleton Chrome DevTools Protocol server into Firefox
Categories
(DevTools :: General, enhancement, P3)
DevTools
General
Tracking
(Not tracked)
NEW
People
(Reporter: spinda, Unassigned)
References
(Blocks 1 open bug)
Details
Implement a Chrome DevTools Protocol server into Firefox which fully supports the HTTP portion of the protocol (querying version information, enumerating available pages, opening new tabs, switching the active tab) and supports an initial subset of WebSocket commands and events.
This can be based on the cdp [0] and tokio-cdp [1] crates, which have been used to build a similar feature into Servo [2]. Page.navigate [3] and Page.reload [4] will probably be good first commands to implement.
[0] https://github.com/devtools-html/cdp
[1] https://github.com/devtools-html/tokio-cdp
[2] https://github.com/servo/servo/pull/18133
[3] https://chromedevtools.github.io/devtools-protocol/tot/Page/#method-navigate
[4] https://chromedevtools.github.io/devtools-protocol/tot/Page/#method-reload
Reporter | ||
Updated•8 years ago
|
Updated•8 years ago
|
Priority: -- → P3
Updated•7 years ago
|
Product: Firefox → DevTools
status-firefox57:
affected → ---
Comment 2•7 years ago
|
||
This bug has not been updated in the last 3 months. Resetting the assignee field.
Please, feel free to pick it up again and add a comment outlining your plans for it if you do still intend to work on it.
This is just trying to clean our backlog of bugs and make bugs available for people.
Assignee: lists → nobody
Status: ASSIGNED → NEW
Reporter | ||
Comment 3•6 years ago
|
||
(In reply to bakhtiyor from comment #1)
any updates of the issue?
I worked on this as an intern project back in 2017. Not sure what happened to it after I left.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•