This repository has been archived by the owner on Feb 26, 2022. It is now read-only.
Bug 597843: remove defaults/preferences/prefs.js from the extension template, other prefs-related cleanup #100
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
…e it has no effect in bootstrapped extensions anyway. While we're here, a couple of changes to default profile prefs: 1) make 'javascript.options.strict' work again by moving it to prefs.py 2) remove prefs not specific to xulrunner from XulrunnerAppProfile 3) create DEFAULT_COMMON_PREFS for preferences common to all applications
… to set development prefs, there's no need to ignore it while building XPI, which is helpful for people packaging non-bootstrapped extensions, which have default preferences they need in production.
This pull request was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
From https://bugzilla.mozilla.org/show_bug.cgi?id=597843: