c2034617f0
2429 default true 67+
2019-04-15 14:59:23 +00:00
6231d6ebed
5000s add new about:config warning pref
2019-04-15 14:54:55 +00:00
411805b05c
2618 no longer hidden 67+
2019-04-15 14:49:22 +00:00
8c12f4bb14
1840 no longer hidden 67+
2019-04-15 14:46:39 +00:00
e3349d0f07
2212 defaults [67+ change]
2019-04-15 14:17:52 +00:00
92082621d6
start 67 commits
2019-04-15 14:15:54 +00:00
54f86f4be6
Update user.js
2019-04-15 12:55:15 +00:00
585415b534
RFP: prefers-color-scheme 67+
2019-04-11 02:02:26 +00:00
99586c4a3b
enabled scopes breakage info, closes #674
2019-04-08 14:24:41 +00:00
8419b4d71b
autoplay option "Prompt" was removed in FF66 ( #686 )
...
* autoplay option "Prompt" was removed in FF66
source: https://hg.mozilla.org/integration/autoland/rev/2e48b6769911
2019-04-09 01:44:11 +12:00
79e316a26f
2618: better info, #682
2019-04-03 10:50:59 +00:00
26a70f3cd7
2618: setup-chrome tag, closes #682
2019-04-03 10:43:44 +00:00
bee47f33cd
66-beta
2019-03-27 04:35:42 +00:00
2fcec590b4
Update user.js ( #676 )
...
- to avoid confusion with the setting tag, split the prefs into separate numbers, thus shove 2031->2031, reuse 2031
- remove the default value notation as Mozilla will roll out default change gradually to users
2019-03-26 19:05:55 +00:00
3c4b312cc7
2030: default didn't change
...
not putting the setup-web tag back in, as users now have site exceptions
2019-03-19 19:58:15 +00:00
0354895a2e
2030: add [setting] for autoplay
2019-03-19 09:00:39 +00:00
462db2062c
2030: remove setup tag
...
If Firefox see fit to set this as 1 by now, then breakage is probably rare, and I'm not encouraging users to reduce security/privacy etc from default
2019-03-17 22:43:27 +00:00
d9e24e5095
Update user.js ( #667 )
2019-03-18 07:07:15 +13:00
b1aa1f5619
2030: default change
2019-03-16 22:51:58 +00:00
a349662f69
66 deprecated prefs
2019-03-16 22:44:24 +00:00
28a7226235
4510: clarify this is the chrome
2019-03-16 22:36:31 +00:00
97f08ad3cd
4504: RFP letterboxing, closes #659
2019-03-16 22:34:45 +00:00
68584a3397
some 2505+RFP clarity, closes #661
2019-03-13 15:15:23 +00:00
8b4f45774a
4607+RFP clarity, closes #656
2019-03-13 14:46:33 +00:00
f8428dcc0a
a better test
...
- more metrics covered/displayed
- test page site is https
2019-03-07 14:55:03 +00:00
6d6cd5f410
2802 applies to 2803, closes #658
2019-03-05 03:26:39 +00:00
eae8434853
start 66 commits
2019-02-26 07:53:21 +00:00
2cff24f12e
65 final
2019-02-26 05:42:32 +00:00
60be8be5ec
UNC and extensions, closes #651
2019-02-17 03:51:44 +00:00
981dd83c15
clarify themes info, closes #648
2019-02-17 16:34:34 +13:00
5c703f0262
65-beta
2019-02-09 10:05:45 +00:00
de0ebbed21
0343: even MOAR clarification
2019-02-08 11:38:17 +00:00
e448015704
0343: clarify where
...
TAAR is extension recommendations in the "Add-ons Manager" (not sure how it's displayed)
CFR is extension recommendations as you browse the web, via a drop down panel
2019-02-07 16:55:04 +00:00
d3b1ed45ad
RFP: UA spoof is now 60+8's
2019-02-07 15:14:08 +00:00
ed140425ea
move shit around
2019-02-08 03:41:23 +13:00
3847f97f41
some more 65+ diffs, #610
2019-02-07 13:41:15 +00:00
d81e8ae583
i need a break
2019-02-07 11:11:16 +00:00
7a8381d894
typo
2019-02-07 11:01:31 +00:00
649699ad22
0609: disable connectivity service #610
2019-02-07 11:00:07 +00:00
1d5289dd94
RFP 67+
2019-02-06 16:59:28 +00:00
74c8f294d6
0306: extension metadata, closes #615
2019-02-05 04:51:07 +00:00
a0508eccf6
capital letter after [note]
2019-02-04 13:41:56 +00:00
25acd9f63e
2703 again
...
- description needs to stay changed from just cookies since it also clears site data
- keep the info about n days out of it, it's just messy (ESR users should be on version 60)
- get the values correct (I mixed them up earlier)
- fixup [setting] path
- leave in one (of two) extra [notes] I previously added
2019-02-04 13:40:45 +00:00
74a08114a8
2701: refix setting
2019-02-04 13:28:29 +00:00
71ffc661b2
2701 again
2019-02-04 13:26:19 +00:00
e432a22693
0306: moar info #615
...
see https://github.com/ghacksuserjs/ghacks-user.js/issues/615#issuecomment-460243162 - checking for updates is not a trigger, having an update **and** applying it is
2019-02-04 13:08:41 +00:00
f06c78f897
update cookie settings info
2019-02-05 02:00:19 +13:00
847eb80877
0306 => inactive, closes #615
...
whatever we thought it may have done in the past, it doesn't do that now as far as we know. And it's not an issue since we allow extension update-CHECKs anyway.
2019-02-04 06:39:29 +00:00
ec0e58099f
pointer events -> RFP ALTS
2019-02-01 13:53:04 +00:00
e6eb473071
dom.storage_access.enabled
...
regardless of this pref setting: the permissions.sqlite file will still be abused to store a flag for this for every single site you connect to (as third party?) - fun.
2019-02-01 13:41:00 +00:00
