-
Notifications
You must be signed in to change notification settings - Fork 514
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider including stricter user-overrides.js with release #1903
Comments
i'm not interested in providing an overrides file - the entire user.js is a template and users should already be adding overrides (even I have some) .. so declined, sorry, not sorry :) |
ikr! lets blame @morganava ... also I think @PieroV would love doing more builds, also one for gecko on iOS for the EU :D |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the default changing to FPP, it may be preferable to include an overrides file with the strictest prefs for those that don't mind the breakage that comes with RFP but perhaps not monitoring current issues. I saw your overrides listed in a comment in #1804 which I am using and do prefer but not sure if everyone saw. Firefox with the strictest settings is as good as we can get for those on aarch64 IMO since TB or MB do not have aarch64 releases so it's nice to easily get as close as possible since there's no other option. I think the best would be to have two different user.js files in each release (one of them stricter) but that would mean changes to updater.sh to ensure proper tracking of which is which.
The text was updated successfully, but these errors were encountered: