Why does this use top-level browsing context scoping? If A nests B and we run the event loop for B, we end up passing A's browsing context to the Long Tasks API from HTML's event loop algorithm. This seems rather weird. (And that in turn will do something with both A and B.)