ToDo: diffs FF66-FF67 #687
Comments
some bugzilla tickets
|
|
While looking at https://bugzilla.mozilla.org/show_bug.cgi?id=1519276 I got #688 You can check your DateTime on https://classify-client.services.mozilla.com/api/v1/classify_client/?format=json |
|
When the preference is set to true, the extensions are enabled by default in private windows. Regardless of this pref, all already installed extensions at the time of updating to 67 will remain to be allowed in private windows unless you go in and toggle them to off.
true = allow in private browsing. It sounds like your testing suggests that the pref is doing the opposite of what it's supposed to do!? Are you sure you tested correctly? |
the 3 security.certerrors.mitm.* might be worth considering since it's an outgoing connection that some people might not want |
This comment has been minimized.
This comment has been minimized.
|
67.0 changes since 67.0b18 newpref("browser.contentblocking.introDelaySeconds", 1800);
pref("browser.tabs.remote.useHTTPResponseProcessSelection", false); // "new" with value true in 67.0b18
pref("network.protocol-handler.external.res", false);
pref("trailhead.firstrun.branches", "control");removed, renamed or hiddenpref("browser.newtabpage.activity-stream.feeds.migration", true); changed
EDIT : updated 1st post |
|
Here's whats left. At this stage IDK if there's necessarily anything else that needs to be added. @earthlng what are your thoughts I never know what to do with AS shit. These are false, so I think we can just ignore them pref("browser.newtabpage.activity-stream.discoverystream.endpoints", "https://getpocket.cdn.mozilla.net/");
pref("browser.newtabpage.activity-stream.discoverystream.optOut.0", false);
pref("browser.newtabpage.activity-stream.telemetry.structuredIngestion", false);
pref("browser.newtabpage.activity-stream.telemetry.structuredIngestion.endpoint", "https://incoming.telemetry.mozilla.org/submit/activity-stream");IDK what this all means, IDK if false is good or bad. Also keep in mind that a lot of things like this are off when first introduced (see more examples below) and get flipped in tests or when ready. If it's not that important, then maybe not worth adding? - @earthlng pref("browser.tabs.remote.useCrossOriginOpenerPolicy", false);
// https://bugzilla.mozilla.org/show_bug.cgi?id=1529004
pref("browser.tabs.remote.useCrossOriginPolicy", false);IDK WTF this is pref("browser.tabs.remote.useHTTPResponseProcessSelection", false);
// https://bugzilla.mozilla.org/show_bug.cgi?id=1528360
// https://bugzilla.mozilla.org/show_bug.cgi?id=1522637These look cool. Note that we have SW's disabled. And that Mozilla will enable these soon. So again, IDK if it's worth adding. pref("dom.webnotifications.requireuserinteraction", false);
pref("permissions.desktop-notification.postPrompt.enabled", false);
// add these inactive true?
// the first blocks WN until you have interacted with the site
// the second, 99% sure, adds an icon in the urlbar to visually alert you, and so you can click it to change the WN permission (for that site)
// test: https://www.bennish.net/web-notifications.htmlAgain. We clear cookies on close, or users use an extension (suckers!), or block them outright (like a ninja master). This will get changed when they play with it in studies. Might be ok to add inactive as a FYI? pref("privacy.documentCookies.maxage", 0);
// https://bugzilla.mozilla.org/show_bug.cgi?id=1529836Not looked at yet pref("signon.autofillForms.autocompleteOff", true);Could maybe add this as a FYI to the passport section. Allows saving of pw's when in PB mode. pref("signon.privateBrowsingCapture.enabled", true); |
WN = Web Notifications ... I know you're doing a great job and handle settings so frequently that acronyms become obvious, but for those who wish to learn maybe having the full denomination rather than the acronym would help.... |
Service Workers. We might need to add a section to the wiki just for acronyms at this point... 😹 |
|
I just watched Captain Marvel .. i know what u are now 🐈 |
|
Service Workers, OK I remember/know that. Anyway, thanks @claustromaniac |
Yes I think that's fine, because
yes. Could be handy for people who don't clear cookies on shutdown
|
When or if you do the changelog, you'll see that the effective difference to your browser is almost nothing. Almost everything that was removed was already covered by another active pref, or was already at default, or was inactive (the SB ones are three ticks in the UI, sorry for the loss of that info). Once you ignore all those changes, then not much was actually changed. The few things that were changed, stemmed from all the things that people found troublesome, or overrode (not everything was changed, just revisited). They changed because they don't make sense any more (it's still a template). It's really not that much.
Well, I hope you do get back in sync. Nothing of any real importance was lost. Anything from changelog that you feel strongly about, can always be put back.
The password one was just a suggestion - inactive for those who wanted to keep the status quo as the old PB mode, but you're right, it's just extra crap. Users have to tick "ask to save passwords" for starters (options UI). And then when using passwords FF prompts to save them. And it would still do the same in PB mode (default true on the new pref). Web Notifications: we disable Service Workers only. That's all that is needed to stop SW and Web Notifications and Push. I was just suggesting maybe adding the two WN prefs for those who want SW+WN but could then limit them. But TBH, I really can't see the point: as I said earlier: these will get flipped when ready. It's these sort of entries that just end up being the items we end up removing down the track as dead wood, matching default. Thanks for your thoughts on the others |
|
@earthlng close this when you want me to do a release, thanks |
|
^^ see my comment here. Other than that I think we're done here. Feel free to close and do a release. Thanks mate |
FF67 is scheduled for release
14th21 MayFF67 release notes [when ready]
FF67 for developers
FF67 compatibility
FF67 security advisories
155 diffs ( 94 new, 37 gone, 24 different )
new in v67.0:
5000s- 1500542 - 6231d6e2618move to RFP ALTs - 57339d0FYI
removed, renamed or hidden in v67.0:
DONE- dfab1515000s- 15289532428- 1485264changed in v67.0:
2212- e3349d02030- 6f76a9b10202662ignore
click me for details
==NEW
==REMOVED or HIDDEN
==CHANGED
The text was updated successfully, but these errors were encountered: