Hi Colleagues! I'm removing TabGroup (and by virtue of it becoming just an indirection I'm also removing SystemGroup), and this affects you if you're doing event dispatching in a handful of ways.
TabGroup was the way in wich Quantum DOM would manage how runnables were scheduled, but with Fission, TabGroups have become replaced by BrowsingContextGroup. This removes the need to be able to dispatch runnables to TabGroups (and SystemGroup). Quantum DOM introduced the concept of labelling, and this is something that we're keeping. It's used by about:performance to tie CPU time to documents within a tab. For this reason we're keeping SchedulerGroup around to be able to dispatch a runnable when you know which DocGroup it concerns. All the dispatches to TabGroup and SystemGroup will be replaced by a common version in SchedulerGroup. This implies that all dispatches will be done to the main thread. This is actually not different from how it is currently, but us now more explicit. Getting an event target from TabGroup and SystemGroup will be replaced by getting the main thread event target. This is also not different from how it is currently, but again removes a layer of indirection. For the cases where we've had throttled event queues, those event queues have been made explicit and moved to their respective use site. If you're uncertain of how this affects you, you can reach out to me on slack or riot. Thanks, farre _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
