Only disable HWA in m-c build and for local dev #18255
Merged
Conversation
This file contains 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
This way, we keep pdf.js working as before except for Firefox.
|
Given that we've historically seen loads of bug reports for Chromium browsers where the issue goes away when HWA is disabled in the browser, do we actually want to make this change? |
|
The context of this PR is the discussion starting at #18238 (comment) While disabling HWA is known to fix some bugs, the question is whether disabling it unconditionally is going to have a net positive effect. |
Rob--W
approved these changes
Jun 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 way, we keep pdf.js working as before except for Firefox.