Tracking bug for the remotable inspector.
6 years ago
Whiteboard: blocking-development → [blocking-development][b2g]
Is there anything we can do on the b2g side to help there?
(In reply to Vivien Nicolas (:vingtetun) (:21) from comment #1) > Is there anything we can do on the b2g side to help there? Nothing in particular. Dave is working on it. And as soon as I'm back online, I'll also be working on this. If you have any question, ask :jwalker.
Here's a quick status update: I'm basing my work on the prototype at https://github.com/campd/mozilla-central/tree/async-inspector . I took some time to make the actor work quite a bit better (particularly wrt memory management), but the frontend work should progress from prototype to patches more quickly. Most of the actor work needed is in patches on dependent bugs.
Let's do any further work in individual bugs.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Assignee: nobody → dcamp
Target Milestone: --- → Firefox 26
You need to log in before you can comment on or make changes to this bug.