>>>>> "Bill" == Bill McCloskey <wmcclos...@mozilla.com> writes:
Bill> As part of the Quantum DOM project, we're going to be "labeling" all Bill> runnables in the browser to say which document they're operating on. I wonder whether this can be used to fix the various "run to completion" bugs we've encountered in the debugger. I don't know if I understand the problems there well enough to do them justice, but basically the issue is that the debugger needs to delay some runnables but not others, and the approach currently used lets some slip through. This shows up in a very confusing way for the user, like some XHR callbacks still being invoked while supposedly paused in the debugger. The meta bug for the devtools side of this is: https://bugzilla.mozilla.org/show_bug.cgi?id=1074448 It has links to all the scenarios where we've encountered the bad behavior. The wish-list fix is: https://bugzilla.mozilla.org/show_bug.cgi?id=715376 aka "implement per-page event queue, to allow timeout grouping/prioritization/etc". I wonder specifically if Quantum DOM is going to fix this one. thanks, Tom _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
