Devtools support is broken

[delan]

Devtools support seems to be broken as of Firefox 110.

The connection prompt works, and there are no messages afterwards under RUST_LOG=trace,

but in about:debugging, there are no tabs:

[sagudev]

https://servo.zulipchat.com/#narrow/stream/263398-general/topic/devtools

[fabricedesre]

I started to look at that, and have WIP fixes: runtime info, tabs and process list are working. Still need to fix tab inspection.

[fabricedesre]

I'm following up my debuggin with Gecko devtools team in https://bugzilla.mozilla.org/show_bug.cgi?id=1836856

[sagudev]

Any progress?

I would really like to use it for console.

[fabricedesre]

Sorry I didn't have time to look at it more yet. My current changes are here: https://github.com/fabricedesre/servo/tree/devtools

Next step is to implement the frame watcher actor afaict.

[ochameau]

FYI, I provided some up-to-date documentation about firefox protocol:
https://firefox-source-docs.mozilla.org/devtools/backend/actor-hierarchy.html
This isn't necessarily complete, but should cover most high level actors.

And also some unit tests which highlights the typical JSON packets transfered to debug a page:
https://hg.mozilla.org/integration/autoland/file/aceb5aaeb650bdd368d51487444ae2eeb497f028/devtools/server/tests/browser/browser_document_rdp_basics.js

Hopefully all this would help replicate a rust implementation for servo.

[spookyvision]

suggestion: update the devtools wiki page to clarify that devtools support is currently broken

[oSoMoN]

Following up on #32227, I'm interested in working on this. Can someone please assign to me?

[sagudev]

Following up on #32227, I'm interested in working on this. Can someone please assign to me?

I think Devtools support is part of outreachy, so someone might already be assigned. @mrobinson?