[Bug 15007] Add an API to queue a task

https://www.w3.org/Bugs/Public/show_bug.cgi?id=15007

--- Comment #31 from Simon Pieters <simonp@opera.com> 2011-12-07 07:57:13 UTC ---
(In reply to comment #30)
> "setTimeout() is throttled when nested" is not a reason to invent a new API
> here. Any API we invent here will eventually end up throttled.

We already have APIs all over that queue a task to fire an event, which can be
used and is being used to implement polyfills for what is being requested in
this bug. They are not throttled today, and I don't see why they would be in
the future (throttling them would hurt perf benchmarks for one). setTimeout was
throttled *from the beginning*, which is why it has to be today. An API that is
not throttled from the beginning does not produce a legacy that expects
throttling.

> Seems to me there's already several quite legitimate and simple ways to do
> this, as discussed above. I don't really see an argument for yet another new
> feature.

It's hard to implement a bug-free polyfill, as evidenced by the comments above.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 7 December 2011 07:57:22 UTC