On Fri, Mar 11, 2022 at 2:15 AM Ht Millican <[email protected]> wrote:
> I don't know maybe just need some incentive tired of the short end of > the stick I mean all the time and effort u guys put u can't do it > > On Fri, Mar 11, 2022, 3:53 AM Anne van Kesteren <[email protected]> wrote: > >> On Wed, Mar 9, 2022 at 8:16 PM Etienne Pierre-doray >> <[email protected]> wrote: >> > As an example, this change breaks the assumption that setTimeout(0) >> causes micro tasks to run in at least one case in Chrome tests ( >> crbug.com/1302309). >> >> This is something you plan to fix, right? setTimeout no longer >> adhering to task semantics seems egregious. >> > This proposal doesn't change task semantics or when microtask checkpoints run, only the nesting level at which the 4ms clamping starts. I think this is a timing issue with that particular test; it looks like it’s depending on the relative order of setTimeouts and stream writer promise resolution, and changing when we clamp setTimeout affects that order. We'll look into the test and fix the ordering assumptions if they're invalid. -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADnb78jSSZuZTNnQ1me83xUD7XO82PKS4btmPKBGCkkqukxh_Q%40mail.gmail.com >> . >> > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKXGoJ11b63feEoRH%2BRLu8e_%3DTy2%2BPmH6pjHAD0LEKbP_pmCfg%40mail.gmail.com.
