--- Comment #2 from Brendan Shanks bshanks@codeweavers.com ---
The latest stable release of Chrome on Windows (109.0.5414.119/.120, released
yesterday) should now have the fix.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.