186444 2018-06-08 13:54:55 -0700 [CoordGraphics] CompositingRunLoop assumes a WorkQueue has a RunLoop 2019-03-01 10:37:15 -0800 1 1 1 Unclassified WebKit WebKit2 WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 195208 https://bugs.webkit.org/show_bug.cgi?id=195208 P2 Normal --- 186364 1 don.olmstead webkit-unassigned cgarcia fujii mcatanzaro ysuzuki zan oldest_to_newest 1431396 0 don.olmstead 2018-06-08 13:54:55 -0700 CompositingRunLoop has a method runLoop() which gets the runLoop of a WorkQueue. This is GTK and generic run loop specific so WinCairo cannot currently use this. 1431529 1 ysuzuki 2018-06-08 20:37:03 -0700 I don't think WorkQueue should expose RunLoop in its member function since it's implementation detail. If handling RunLoop is required, it means that WorkQueue abstraction is too high to use there. CompositingRunLoop should use RunLoop instead of WorkQueue I think. 1510902 2 cgarcia 2019-02-28 05:16:20 -0800 We have two options here, either use our own thread with a run loop, or keep using a work queue, but making the timer creation platform specific (I guess in windows you could add a WorkQueue::timerQueue() similar to dispatchQueue() used by cocoa and runLoop() used by glib and generic) and create the timer with CreateTimerQueueTimer(). 1511394 3 cgarcia 2019-03-01 06:58:46 -0800 This will be fixed in bug #195208 1511454 4 don.olmstead 2019-03-01 10:37:15 -0800 *** This bug has been marked as a duplicate of bug 195208 ***