domenic
commented
2 years ago Oh wow, fascinating! I'm glad we changed that to bring this up... as it is written currently, clearTimeout() would be able to cancel geolocation!
(Or maybe not, since step 5.5.5 adds it, and then synchronously step 5.5.7 removes it, so it actually never used the list of active timers?)
Deciding whether you want to use "run steps after a timeout", versus just doing the waiting yourself, depends on whether you want the following characteristics:
- The timeout is suspended while the page is in bfcache or while the worker is suspended
- The timeout is allowed implementation-defined fudges, usually to align with CPU wakeups (e.g. on battery)
- The timeout must extend idle deadline computation, i.e. requestIdleCallback()
- The timeouts are ordered, e.g. if two timeouts with the same millisecond value started at the same time must run in order
If you want all of those characteristics, then "run steps after a timeout" is for you. Otherwise, you'd want to manually wait, which is pretty simple: just have some in parallel steps "1. Wait for X milliseconds 2. Do the thing."
marcoscaceres
@domenic, exciting to see https://github.com/whatwg/html/commit/19aad5836e2d128c7c87f152e6e3bc6c4ff32d19 updating the timer related prose/algos in HTML.
Geolocation was depending on the "list of active timers" as part of the request position steps. I'm wondering if you can provide us with some guidance for integrating with the newly exported "run steps after a timeout"?... also, should we use the new timer task source?
(I'll slap something together... is it ok if I bug you for review?🙏)