Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 9c0e11595b57609920d4a83dff22f45a56722b4a
https://github.com/WebKit/WebKit/commit/9c0e11595b57609920d4a83dff22f45a56722b4a
Author: AbdAlRahman Gad <[email protected]>
Date: 2026-05-06 (Wed, 06 May 2026)
Changed paths:
M Source/WTF/wtf/RunLoop.h
M Source/WTF/wtf/win/RunLoopWin.cpp
M Tools/MiniBrowser/win/WinMain.cpp
Log Message:
-----------
[Win] Improvements to run loop timer resolution & Make MiniBrowser use
WTF::RunLoop
https://bugs.webkit.org/show_bug.cgi?id=284823
Reviewed by Don Olmstead.
WM_TIMER has a 10ms resolution, which means we can't hit 60fps on
requestAnimationFrame. By using MsgWaitForMultipleObjectsEx and
maintaining our own timer queue we can get better timer resolution.
Make Windows MiniBrowser run the UI thread with WTF::RunLoop::run(),
letting WTF own the main run loop while still giving MiniBrowser a chance
to consume Win32 messages before the default
TranslateMessage()/DispatchMessage() path.
Co-authored-by: Ian Grunert <[email protected]>
Canonical link: https://commits.webkit.org/312750@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
