[Webkit-unassigned] [Bug 164193] Implement requestIdleCallback

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=164193

--- Comment #14 from Michael Catanzaro <mcatanzaro at gnome.org> ---
(In reply to Alexandre Dieulot from comment #9)
> May we know what’s blocking WebKit from shipping requestIdleCallback, if
> anything? Has it just been utterly deprioritized? Nearly all the
> dependencies of this ticket haven’t moved in the last three years. It’s
> bewildering.

Well nobody has submitted any pull requests. It won't fix itself; help welcome.

Anyway, good thing you pointed me to the dependent issues, because now I see there is the DOM-level EventLoop.cpp, WindowEventLoop.cpp, WorkerEventLoop.cpp, which I didn't know about. I had only been thinking in terms of RunLoop.cpp. Since it's a wrapper over Timer and RunLoop, I had hoped that maybe it's just one more layer to deal with, but nope there's a complicated specification at https://html.spec.whatwg.org/multipage/webappapis.html#event-loops which I haven't read and which should ideally be understood before proceeding. But it looks seriously complicated, and I don't have enough time or expertise to understand it, so I won't try. (Then there's also a request idle callback specification https://w3c.github.io/requestidlecallback/ but fortunately that one is simple and more or less exactly what I expected.)

Regarding the dependent issues: maybe these are required to implement that event loop spec as expected, but frankly I only have a couple afternoons to spend on this and I only care about being able to create pull requests on github.com and nothing else, so I'm going to ignore those. ;) None look required for a minimum viable implementation. Bug #203137 is about timers and not idles, bug #203667 is about media loading, bug #203840 is basically what I wrote in comment #13 above, and bug #206676 is about a test that fails because this API doesn't exist yet.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230314/9d7e7204/attachment.htm>