ToDo: diffs FF76-FF77 #949
Comments
some bugzilla tickets
|
|
I think we can remove Anyway: maxRichResults (c) and autofill (d) have nothing to do with privacy and oneOffSearches (e) doesn't either, but at least that's deprecated now. I get the shoulder surfer aspect of it, but that's on the end user: even Tor Browser doesn't cover this. You can't code OpSec. TBH: if you're like me and don't like the urlbar doing anything except being static (no suggestions, not UI changes, no movements, no color changes), then I've simply been using chrome css |
|
^^ I am using |
|
Telemetry is disabled and reseting this in the user.js would be useless. |
|
#923 is an issue again in FF77 !! (but it only affects Windows) The good news is that the problem is apparently already fixed in FF78+ (1634267). useDOSDevicePathSyntax=true is supposed to fix issues when file paths exceed the path limit on Windows so I think the better option is to just set 0709 to false. Linux and Mac users can add 0709 to their user-overrides if they deem it necessary but it's a pretty edge-case protection anyways and losing it for 1 release isn't too bad either, IMO. |
|
speaking of breakage - did you get that email I sent about changes to the origin attributes and thus to the naming conventions? I don't have the email anymore so I can't find the ticket quickly. I hope we don't end up with a migration mess like when they applied OA to extensions |
|
this is the link you sent me: https://bugzilla.mozilla.org/show_bug.cgi?id=1558932#c16 FYI just found these 2 in FF78beta1 which sound like they're related: pref("privacy.dynamic_firstparty.use_site", true);
pref("privacy.firstparty.isolate.use_site", false);update: both prefs were implemented in 1637516 |
|
updated OP for the final release. |
|
Sorry if I missed this somewhere, but Firefox release on Windows just updated to v77. With ghacksuserjs, extensions seem to be messed up. For example, trying to view the uBlock Origin settings page only shows the header bar but no content. This issue seems to affect other extensions as well. Without ghacksuserjs, there is no issue. Suggestions on a setting I should adjust? Thanks!
|
|
@collinbarrett see #951 |
It's |
|
OT: anyone know the css for userChrome to modify the awesomebar and searchbar blue outlines when they have focus (as show in the top part of the pic)
|
|
@collinbarrett , @crssi 05580f5 Added to the master so no-one needs an override: I'll remove it some time well after 78 lands and it's known to be fixed |
|
If anyone has a reddit account ... this totally looks like the UNC / DOS Path problem - just point them to #923 - TIA |
Maybe https://www.reddit.com/r/FirefoxCSS/comments/fxez4e/remove_new_megabar_grow_shrink_effect/fmvadbr/ |
I use this. |
|
^^ thanks (I'll check it out), and @gwarser that helped with the css property name this works for urlbar: cannot for the life of me get the selectors right for searchbar (the one on the right) #urlbar, .searchbar-textbox {
--toolbar-field-focus-border-color: #202124 !important;
}
|
|
my bad, didn't realize you needed both, this should work. |
Excellent .. have a socially distanced hug 🤗 |
|
I think they fully broke 1633. Now its user_pref("ui.prefersReducedMotion", 1);. Can somebody confirm or its my imagination? Classic urlbar CSS for Firefox 77 |
|
Yes. Im talking about toolkit.cosmeticAnimations.enabled in personal section. For exemple look on refresh page button with ui.prefersReducedMotion;1 and without it. |
|
Here's the meta bug - there are at least 5 bugs in all of the ones for FF77 (I queried all 77 bugs) where the title indicates a change to UI animations to use PRM The pref in the personal section will eventually be deprecated. Just use your custom chrome css. But long term the idea is that RFP exempts the UI (chrome) etc. Yes, javascript can query what your prefers motion and prefers color etc are - so RFP locks that down to the default, otherwise it's just another bit of data that can be used overall in your fingerprint |
Quoting FF Devs: "We can keep FPI/dFPI have the same behavior here, and (if necessary, ) use another pref to control whether we should use site or not. The pref may keep some backward-compatibility for special cases, e.g. Tor Browser, and we can turn this pref on to use "site"." |
|
"The first pieces of dynamic first-party isolation (DFPI) landed in Nightly. DFPI is an experimental approach to isolating all third party cookies and storage, similar to FPI (which is enabled by default in the Tor Browser and is also supported by Firefox). The most important difference between DFPI and FPI is that DFPI will adhere to exceptions granted through the storage access API and thus ensure better web compatibility. " https://wiki.mozilla.org/Firefox_Security_Newsletter/FSN-2020-Q1 |
|
Thanks. I'm aware of all that and for the user.js I'm tracking it in #930 Edit: if FPI is on, dPFI is ignored, and until dFPI is enabled by default (which could be quite some time) there's nothing to do: and the longer it takes, the more bugs they fix and the more dFPI covers etc |
FF77 is scheduled for release June 2nd
FF77 release notes [when ready]
FF77 for developers
FF77 compatibility
FF77 security advisories
109 diffs ( 58 new, 33 gone, 18 different )
new in v77.0:
removed, renamed or hidden in v77.0:
ALL DONE- f6e6de80850epref("browser.urlbar.oneOffSearches", true); - 16289262605pref("browser.tabs.remote.allowLinkedWebInFileUriProcess", false); - 1603007changed in v77.0:
ignore
click me for details
==NEW
==REMOVED or HIDDEN
==CHANGED
The text was updated successfully, but these errors were encountered: