summaryrefslogtreecommitdiff
path: root/libre/iceweasel/vendor.js.in
AgeCommit message (Collapse)Author
2023-09-12[iceweasel]: use gnuzilla 'mozzarella' website for add-ons searchbill-auger
2023-02-08libre/iceweasel: 109.0grizzlyuser
* Update version and patches according to upstream changes * Remote Settings patching: fix modification of response headers after local fetching of JSON file from bundled resources, because response headers became immutable in this version. * FSDG: Remove some values of preferences containing URLs to AMO (see commit messages from 9002-FSDG-preference-defaults.patch) and add a corresponding validation to PKGBUILD. Also remove some related property overrides from vendor.js.in and patch them in the code, please find the reasoning in the same patch. Also remove extensions.htmlaboutaddons.discover.enabled preference override from vendor.js.in, because it was removed upstream in [1]. * Remove technical patch for python-zstandard 0.19, fixed upstream * Remove RENAME_PROFILE logic from PKGBUILD, as the comment from that code suggests to remove it in 2023 [1] https://hg.mozilla.org/mozilla-central/rev/e542391fb8c5
2022-09-03[iceweasel]: fix 'sync' bugbill-auger
2021-07-29[iceweasel]: set about:addons link to parabolabill-auger
2021-05-10[iceweasel]: use default user-agentbill-auger
2021-04-08libre/iceweasel: refactor some prefs overridesgrizzlyuser
Preference overrides from vendor.js are not connected to the code, so they tend to bit rot quite quickly. Also, they only hide the problem, because the source code still contains references to nonfree stuff. Patching has a downside too. If upstream adds an override for some patched preference in a new place, it's likely to take precedence over the patch. Solution for this problem is TBD. But there are ways to override our vendor.js too, so either approach is prone to this. For now, go on with the patching approach. Also drop the override for ui.key.menuAccessKeyFocuses as I don't see how this is related to freedom issues. Let's stick as close to upstream as possible. geo.wifi.uri was probably removed upstream as I wasn't able to find it anywhere in the source tree.
2021-01-12libre/iceweasel: Drop old search engine patchinggrizzlyuser
Legacy search configuration has been dropped upstream [1]. It needs to be done by new method now. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1619926
2020-10-12libre/iceweasel: Disable remote search configgrizzlyuser
2020-07-10libre/iceweasel: Update data reporting preference overridesgrizzlyuser
Because data reporting is now hopefully disabled via build config options, reviewed some of the related preference overrides: Removed the following preferences: datareporting.healthreport.uploadEnabled defined only if MOZ_SERVICES_HEALTHREPORT is defined, see modules/libpref/init/all.js datareporting.healthreport.about.reportUrl Removed upstream, see: https://bugzilla.mozilla.org/show_bug.cgi?id=1352497 Can be found only in some test files datareporting.healthreport.documentServerURI Probably have been removed too, documentServerURI can now be found only in obsolete documentation and some tests healthreport.uploadEnabled cannot be found alone in source tree. Only datareporting.healthreport.uploadEnabled can be found. datareporting.policy.dataSubmissionEnabled defined only if MOZ_DATA_REPORTING is defined, see modules/libpref/init/all.js datareporting.healthreport.service.enabled could find only in some test files datareporting.policy.firstRunTime datareporting.policy.dataSubmissionPolicyVersion could not find in source tree Also checked the following preferences: toolkit.telemetry* still available in the code, so have not removed them pref("toolkit.telemetry.server_owner", "User"); This is just a nitpicking probably, because upstream preference says "Mozilla" instead. And that is not true, because of the following override in vendor.js :) pref("toolkit.telemetry.server", "127.0.0.1"); Signed-off-by: Andreas Grapentin <andreas@grapentin.org>
2020-04-18libre/iceweasel: changed prefs to make jitsi work <3Andreas Grapentin
2020-03-27libre/iceweasel: Adjust vendor.js preferences for search engines and addonsgrizzlyuser
This is mostly related to a recent switch of about:addons from XUL to HTML [1]. extensions.webservice.discoverURL has been removed upstream, see [2]. extensions.getAddons.search.url seems to be removed as well, but could not find any proofs except that source code search doesn't find it anymore. Couldn't see any effect from it either (see [4]). That's why removed those two. Also changed the search engines URL to a more appropriate one, and also disabled 'Recommendations' section the same way Tor Browser Bundle does this [3]. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1558982 [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1544011 [3] https://trac.torproject.org/projects/tor/ticket/22073 [4] http://kb.mozillazine.org/Extensions.getAddons.search.url Signed-off-by: Andreas Grapentin <andreas@grapentin.org>
2020-03-13Make extensions actually work on Mozilla domainsgrizzlyuser
Single previous pref is not enough, effect is seen only with both. Signed-off-by: Andreas Grapentin <andreas@grapentin.org>
2020-03-13Disable 'What's New' gift icon in toolbar and main menu.grizzlyuser
Signed-off-by: Andreas Grapentin <andreas@grapentin.org>
2020-01-19[iceweasel]: rework patches for v72.0.1bill-auger