Enhance Compatibility Guide for macOS Users with Apple Silicon CPUs #2594
Conversation
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
Member
|
It's already covered in these places:
If anyone hits the issue, they'll likely search for their issue before reading all the documentation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This pull request introduces an important update to the README and
uc_mode.mddocumentation to address a compatibility issue faced by macOS users with Apple Silicon CPUs (M1/M2). The update provides clear instructions for installing Rosetta, enabling these users to successfully run SeleniumBase in UC Mode without encountering the "bad CPU type" error.By incorporating these instructions, I was aiming to improve the setup experience for a significant portion of the user base, ensuring that developers using the latest macOS hardware can leverage SeleniumBase's full capabilities without friction. This contribution underscores my commitment to supporting a diverse range of environments and configurations, facilitating wider adoption and user satisfaction.