chore: replace JIT site setting text to be more accurate#769
Merged
Conversation
Up to standards ✅🟢 Issues
|
RKNF404
changed the title
RoyalOughtness
requested changes
Jun 7, 2026
RoyalOughtness
approved these changes
Jun 7, 2026
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
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.
Chromium upstream doesn't use the same preference to disable JS JIT, only optimizers. We disable JIT in whole.
This causes some confusion in regards to how our pref works and how it differs from the upstream pref. It also makes it easier for users to find the preference when told to disable or enable JIT for a site or extension.