-
Notifications
You must be signed in to change notification settings - Fork 527
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 FF55-FF56 #204
Comments
Onboarding seems a first welcome BS:
|
See here |
Race Cache With Network This is good: And I set logging at minimum: |
I would if I knew what to do |
pref("apz.autoscroll.enabled", false); Safe to ignore : |
pref("intl.regional_prefs.use_os_locales", false); |
|
pref("network.preload", true); IMO, there is no privacy concern here. |
Is there a speculative aspect to that? Could there be cases where a web developer assumes a resource will be needed, but that resource isn't needed because of how the user interacts with the page or has their browser configured? Could that interfere with any addons (create network traffic before they have the context they need to decide whether to block it)? I don't see it included in network.networkPredictionEnabled:
My first impression is that none of those would disable it. I need some caffeine, and your eyes may be better, so: https://dxr.mozilla.org/mozilla-central/source/uriloader/prefetch/nsPrefetchService.cpp. Followup: Quick tests in beta and nightly were consistent with my first impression. |
Yes. On twitter 176 occurences are found, as:
|
not per se afaik. Preload is used to load certain resources with a higher priority than it normally would. That can be used for SEO (=better pagerank for example) |
https://developer.mozilla.org/en-US/Firefox/Releases/56#DOM:
=> disabled with this pref in 56 and fully removed in 57 with 1374460 (they forgot to remove the prefs again though) |
It's a recent feature: http://caniuse.com/#feat=link-rel-preload
Answer here. I see it as a placebo to optimize hogged sites. Currently I'm on the opposite field, as keeping a local copy of some needed scripts for sites to load, while ignoring most of other resources. If interested, see here. |
56b12 changes since 56b1 newpref("apz.second_tap_tolerance", "0.5"); removed, renamed or hiddenpref("extensions.screenshots.system-disabled", true); changedpref("apz.touch_move_tolerance", "0.1"); // prev: "0.03" since the beta branch should have already been merged to release yesterday, I've update the first post with these latest changes. |
moved to 'ignore' from 'new':
=> not messing with memory cache integer values moved to 'ignore' from 'changed':
=> throttle is fine, and touch move tolerance ... who cares update:
|
done or moved to tasks - see first post
pending
moved to ignore:new
|
https://bugzilla.mozilla.org/show_bug.cgi?id=1390346#c25
https://bugzilla.mozilla.org/show_bug.cgi?id=1390346#c33
https://bugzilla.mozilla.org/show_bug.cgi?id=1334550#c25
conclusion: best to ignore this |
Yes
|
btw please check if the prefs that we haven't ignored were actually set to the value the diff says, because I just noticed that they changed something with the omni.ja creation, and the order in which the default preferences files are loaded might have changed. Meaning that if a certain pref exists in 2 or more pref-files and with different values then the output of my diffs-script could be wrong for those prefs. I'll adjust my scripts to detect the preferences files and their load-order automatically rather than hardcoded, which will also guarantee that I won't miss a new or split-out preferences file. |
If trackers can get around extension-based blockers (or the built-in tracking protection) that way, then it's a bug that needs to be fixed :) |
this. I was also wondering if maybe they messed something up which could result in the preferences files being loaded in an unintended order. But somehow it manages to load firefox-l10n.js after firefox.js even though as I understand the code it shouldn't. No idea why.
https://developer.mozilla.org/en-US/docs/Web/HTML/Preloading_content
|
<body>
<script>console.log(navigator.connection);</script>
</body> FF56 Desktop on Windows: |
The transition to SBv4 will be gradual and done via a Shield add-on, which is disabled by user.js. So if you want to switch to it now, you can flip the prefs that the add-on will change: https://github.com/mozilla/sbv4-gradual-rollout/blob/master/bootstrap.js#L16-L20 Otherwise you'll stay on V2 until either a 56 point release flips the prefs permanently, or 57 is released. |
|
v55.0 vs v56.0
150 diffs ( 91 new, 28 gone, 31 different )
Firefox 56 stable lands 2017-09-28
new in v56.0:
extensions.formautofill.experimental
which is deprecated0810
removed, renamed or hidden in v56.0:
ALL DONE - 12f80bd
1385201extensions.formautofill.available
and changed type from boolean to stringextensions.formautofill.available
can be "on", "off" and "detect"1386333changed in v56.0:
0413
1103
(inactive)2031
1110
redundant in 56 due to RFP privacy.resistFingerprinting
ignore
==NEW
==REMOVED or HIDDEN
==CHANGED
The text was updated successfully, but these errors were encountered: