Re: [w3ctag/design-reviews] Scheduling APIs (#338)

My impression, and maybe I misunderstood, is that in the current proposal all existing task sources are lumped into the "default" prioritized task source, with a global FIFO order imposed on them.

If the intent is that this is not the case, and that the prioritized task sources are just adding _new_ task sources, that are unordered wrt each other and with existing task sources, then that eliminates my concerns about the system being too rigid.

That said, it's also not clear to me whether "high priority" means "will run before anything that's low priority" or "will run with higher probability" or something else, or whether this will be up to browsers.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/338#issuecomment-534812474