Re: [dev-servo] What should be the unit of debugging in Servo?

> More generally, tabs, iframes, workers, etc. all make up a set of browsing contexts. The question then becomes: what set of browsing contexts should be the unit of debugging? Or put differently: what set of browsing contexts should be under control of the debugger, so that pausing the debugger

Re: [dev-servo] What should be the unit of debugging in Servo?

I think that each unit of sequential execution should get its own debugger server (so a (same origin?) related browsing context). Then if we want to present a unified interface, we can race-ily pause workers (and cross origin iframes?) and coalesce these things in the UI or via a supervisor task.

Re: [dev-servo] What should be the unit of debugging in Servo?

On Tue, Sep 6, 2016 at 4:35 AM, Boris Zbarsky wrote: > On 9/5/16 8:17 AM, Till Schneidereit wrote: > >> I don't think it makes too much sense to be able to pause completely >> independent browsing contexts that can't possibly interact with each >> other. >> > > There is no such