Razer: point at the confirmed Chrome 153 regression, not a Windows driver - #271
Merged
Merged
Conversation
…ome 153 cause Issue #253's actual cause turned out to be Chrome 153 itself: an A/B test (portable Chromium 152.0.7977.83 vs the same machine's Chrome 153) isolated the regression to the browser build alone -- same Windows install, same drivers, same mouse. The Windows-Update-reinstalled-legacy-driver theory from the earlier PR was tested and ruled out on that same hardware. requestSupportedClient() now checks the Chrome/Chromium major version from the UA string and, when the Razer probe comes back empty on 153+, names the actual cause and workaround (a pre-153 Chromium build) instead of pointing at a driver problem that isn't there. Claude-Session: https://claude.ai/code/session_01XbYSu8D3cu3c7vbEyJbacn
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #270. That PR's Windows-driver theory for issue #253 was tested on the actual reporter's hardware and ruled out; an A/B test (portable Chromium 152.0.7977.83 vs. the same machine's Chrome 153) isolated the cause to the browser build itself.
This replaces the driver-specific hint with a Chrome-version check: when the Razer probe finds nothing on Chrome/Chromium 153+, the error now names the actual confirmed cause and the pre-153 Chromium workaround instead of sending users to check Device Manager for a problem that isn't there.
Claude-Session: https://claude.ai/code/session_01XbYSu8D3cu3c7vbEyJbacn