ToDo: diffs FF56-FF57 #254
Comments
|
@Thorin-Oakenpants I wrote a script that finds the relevant tickets for most pref changes ... bugzilla tickets
|
...safely removing those URLs? dom.ipc.scheduler is related to this and handles tabs like chrome, deferring some heavy loading and prioritising the lighter ones. |
|
@earthling Side by side mode here. |
|
^^ |
|
57b13 changes since 57b3 newpref("accessibility.indicator.enabled", false); // new with value 'true' in Beta 3 removed, renamed or hiddenpref("devtools.webide.addonsURL", "https://ftp.mozilla.org/pub/mozilla.org/labs/fxos-simulator/index.json"); changed
EDIT: first post updated with these changes |
|
|
I agree that WebGL should remain disabled. The Presentation API is weird as well IMO, too many prefs to move them all to the RFP alternatives section. I would keep that where it currently is. |
|
Wow you moved lots of stuff to ignore, nice, thx.
edit: checkboxes and action by Thorin |
That's for a new Safe Browsing service which we've just started implementing. It won't do anything useful until the middle of next year at least. |
|
Yes, you can ignore it until that pref goes from The "password" part is because it aims to defeat phishing pages that steal passwords (e.g. fake login pages). I will definitely blog about it once we've landed all of the pieces :) |
|
^^ why?? it even still exists in the version of 58 I have |
|
The default for |
|
yeah it now defaults to true and therefore the pref obviously still exists and does something. We can remove it from the user.js if you want but it's certainly not deprecated. |
yes it looks weird but
|
|
Tested in FF nightly 58 (2017-09-21) IDK if the behaviour is the same in 57 and/or in newer versions of 58 nightly ! the default values for both prefs are still the same as they are here for 57, openInTabClosesMenu = true and loadBookmarksInTabs = false with only
==> doesn't work at all for menubar > history
and it also works the same for the history items in that menu.
Since I mostly use the bookmarks in the menu bar + middle click + would like the menu to remain open I'll definitely use the 1st pref but don't really need the 2nd pref.
you just click somewhere outside of the menu or close it by clicking on bookmarks or the toolbar icon again.
inactive for both is fine IMO. |
|
|
|
57.0 changes since 57b13 changed
|
|
Linux : 0 disables everything http://www.morbo.org/2017/11/linux-sandboxing-improvements-in.html No hurts here on Nightly, but could break some configurations. In that case, workaround is given in the above article. |
|
there are no prefs for the new permission UI for Camera, etc. In 57 it's just a frontend to edit the sqlite file |
|
I think we should add |
|
It opens a window to |
yes, atm but that might not always be the case especially when they decide to use it for other stuff as well. |
|
|
|
No, it's the same for all of them. FF58 will have new prefs to set the default: pref("permissions.default.camera", 0);
pref("permissions.default.desktop-notification", 0);
pref("permissions.default.geo", 0);
pref("permissions.default.microphone", 0);
pref("permissions.default.shortcuts", 0); |
|
storageManager stuff: localStorage (or DOM Storage as you like to call it) is now cleared on shutdown with |
pref("javascript.options.wasm_ionjit", true);
pref("jsloader.shareGlobal", true);... not messing with this for now. Moved to ignore. When ESR59 is released we can check what TBB does with these 2. |
Where did I say that?
brain 2.0 |
|
I've added it to the sticky |
v56.0 vs v57.0 - 161 diffs ( 80 new, 33 gone, 48 different )
FF57 is scheduled for release 2017-11-14
new in v57.0:
4503- 1384330=> this pref is wildly inconsistent and not ready for prime time
removed, renamed or hidden in v57.0:
ALL DONE - f89bb3f
changed in v57.0:
2706139939827060514081018030421should be covered by RFPsecurity.sandbox.content.levelmoves from 2 to 3 as default (thanks @2glops )=> see ToDo: diffs FF56-FF57 #254 (comment)
redundant in 57 due to RFP privacy.resistFingerprinting
2513for nowignore
==NEW
==REMOVED or HIDDEN
==CHANGED
The text was updated successfully, but these errors were encountered: