-
Notifications
You must be signed in to change notification settings - Fork 523
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
ToDo: diffs FF60-FF61 #426
Comments
bugzilla tickets for some of the remaining prefs
|
It looks like the 4th pref in |
we can also remove |
|
This comment has been minimized.
This comment has been minimized.
61b14 changes since 61b6 newpref("browser.newtabpage.activity-stream.asrouter.snippetsUrl", ""); removed, renamed or hidden
changed
EDIT: updated 1st post |
61.0 changes since 61b14 changed
EDIT: updated 1st post |
// Disable using UNC paths (TBB bug 26424 and Mozilla's bug 1413868)
user_pref("network.file.disable_unc_paths", true); uplifted all the way back to and including ESR52 |
I'd say we force-disable I will definitely also disable tab warmup because I don't want FF to start doing something whenever I hover over a background tab with my mouse. But IDK if it's worth adding under 5000. And lets not forget about this either. The bugzilla for it is still Access Denied. |
|
A fresh bugzilla. And it has Critical Priority. |
this is what it looks like in FF60: 0102+0103 could use a [SETTING-ESR60]. re: 0102 ...
they do
default is 1. In FF61+ it toggles between 1 and 3 0103: I don't really like the "or use an extension". A newtab extension has nothing to do with privacy/security re: 0104: "I do not think the preload does anything any more" - in FF61+ it's obsolete because it's checked together with
it's about what happens on startup and thus fits perfectly where it is right now, IMO. ps: I wouldn't mind activating both 0102 and 0103 and setting them to 0 and "about:blank" to make sure that no websites start loading before all extensions are ready. |
yeah but most people don't use either and IMHO it should be the people using custom urls or extensions that should set an override and not the other way around. Also, people might not realize that when they have a homepage set and startup set to 1 (default) that the site will start to load before all their extensions are ready. |
wow they really fucked it up big time! what a fucking mess Let's just keep it simple and fuck all the infos and settings and shit /* 0102: set a blank startup-, home- and newtab page ***/
user_pref("browser.startup.page", 0); // 0=blank, 1=home, 2=last visited, 3=resume previous session
user_pref("browser.startup.homepage", "about:blank");
user_pref("browser.newtabpage.enabled", false);
user_pref("browser.newtab.preload", false); |
FF61 introduced quite a few changes, including removing the ability to set a blank startpage in the UI, and a new Home options tab with unified Activity Stream (AS) defaults and dropdown options. Because the only way to stop AS on startup is to enforce a blank page (pref 0102), and setting this auto changes `home+newwindow` (0103) and `newtab` (0104) to a blank page, then we're just going to go ahead and enforce that on all of them. For more info see the discussion in #426
AFAIK tab warmup is not about making connections and stuff. It's about doing the visual parsing and processing of the page, DOM, etc so that it displays faster when you switch to that tab. We don't need to add it because it's probably not a big issue and most people are so performance hungry these days. |
211 diffs ( 90 new, 101 gone, 20 different )
FF61 is scheduled for release 26-June
other
0100s
UI changes & cleanup all prefs for home & newtab - c954351new in v61.0:
removed, renamed or hidden in v61.0:
changed in v61.0:
1703 (inactive)
ignore
click me for details
==NEW
==REMOVED or HIDDEN
==CHANGED
The text was updated successfully, but these errors were encountered: