https://bugzilla.wikimedia.org/show_bug.cgi?id=46401
--- Comment #1 from Krinkle <[email protected]> --- Before cssText buffer became async this was fine. In fact, there are various guards to make sure this happens in the same order. This is by design. When we made it async this was done at a low level and escaped the guards at the higher level. We need to fix this by keeping the state of the cssText buffer the same way we do for the code when executing multiple closures. Wait for all asyncs of cssText buffer to have finished before scheduling the asyncs for the closure. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
