• browser.urlbar.suggest.calculator - has nothing to do with this repo - privacy/tracking/etc
• javascript.use_us_english_locale
  • is deprecated in FF119 - which is why you won't find it on searchfox
  • RFP no longer protects your locale (and it was limited to en-US with that pref)
  • at some stage they will hook up locale to match language in some form, which will be better

hidden pref

• it does not show in about:config unless modified (regardless of the value, it is modified)

helperApps.deleteTempFileOnExit - is default true on windows as well

0210 (en-US,en), since RFP no longer matches locale to it, can also be removed or moved to optional. So everyone feel free to use any language. I don't know if I want to keep it in the user.js so prefsCleaner resets it - I would need to check what it gets reset to

update: done - see #1759 and 5759127

https://searchfox.org/mozilla-central/search?q=helperApps.deleteTempFileOnExit&path=&case=false&regexp=false

helperApps.deleteTempFileOnExit - true in firefox.js, false in all.js ... how does this work (rhetorical)?

ignoring android (FYI: @SkewedZeppelin) I guess we just test each platform

• linux is true (but packagers could change it)
• windows is true
• mac (FF119) is false <-- assuming it even applies to mac

So I think we can ignore adding a default note

browser.shell.shortcutFavicons

• https://searchfox.org/mozilla-central/search?q=browser.shell.shortcutFavicons&path=&case=false&regexp=false
  • only has code for widget/windows, i.e not widget/cocoa or widget/gtk etc

So yup, I would say this is a windows only thing

scopes

• https://hg.mozilla.org/integration/autoland/file/909b53b0ab300dcaaed44f901c55eefc8abdb721/toolkit/mozapps/extensions/AddonManager.sys.mjs#l4104 <-- use the commit source so lines don't get fucked up over time

man that's a long one. I use searchfox links to files, but hg.mozilla.org revisions links to lines - but this revision moved the file and didn't change the content we want, so I can't use a sweet short link

lets see what the diffs are:

kaply

1 (SCOPE_PROFILE)
2 (SCOPE_USER)
4 (SCOPE_APPLICATION)
8 (SCOPE_SYSTEM)

moz code

  // General descriptions of where items are installed.
  // Installed in this profile.
  SCOPE_PROFILE: 1,
  // Installed for all of this user's profiles.
  SCOPE_USER: 2,
  // Installed and owned by the application.
  SCOPE_APPLICATION: 4,
  // Installed for all users of the computer.
  SCOPE_SYSTEM: 8,
  // Installed temporarily
  SCOPE_TEMPORARY: 16,
  // The combination of all scopes.
  SCOPE_ALL: 31,

yeah, so that's a good link to add, because that archive is fucking old now and somewhat out of date

actually, fuck that long link ;) it hasn't changed anything, because temporary extensions cannot load on restart.. and I can just add this

 * 1=profile, 2=user, 4=application, 8=system, 16=temporary, 31=all

extensions.webcompat.enable_shim - is runtime - set based on ETP settings = so not "hidden" from sight ever - but technically it is [hidden] by my own definition above

edit: not sure what to do here - I defined hidden above as the way I understood and have used it - so users know why they can't see it, i.e they have to create it and add it

I suspect the other three are runtime as well

What should I do people? give them hidden tags or not?

^ repeat - someone answer ... starting to feel like my childhood in the basement again

maybe managed?

not sure if I want another tag

so here's the thing - I label items to help, but that doesn't mean I have to label ALL items that fit that tag: eg

• not all items have a [FFversion+] - although that's mostly really old prefs
• not all items have a [DEFAULT: - and maintaining it is a burden, especially when it differs per OS
• etc

So i kinda feel like these items that aren't "hidden" in about:config don't really need a [HIDDEN] tag - but I get that as a purist, it is fine. And if someone says "but it's not hidden" I can use the same definition I always have, and then tell them to delete it and reload about:config and tell if they can see it

So the question is - do I add hidden tags or not?

And if I don;t label them, then if someone says .. but that's a HIDDEN pref, please label it - I can say "I only label them when they aren't set by runtime to help users"

So I win either way

So do I add the labels or not ... quick poll of one .. you're up Tad

ok, ignoring them, because of maintenance, plus I am the boss so my second argument wins. just need to check that geo one - because that may only get set if the system supports it

might revisit my last decision .. I mean if it universally (all desktop platforms) has a trash bin symbol, then it's [HIDDEN]

okie dokie

• I updated the wiki description of hidden - https://github.com/arkenfox/user.js/wiki/2.1-User.js

  • except for what are called hidden preferences which will only show when they are modified (i.e. set to any value by the user or browser - they have a trash can symbol for resetting)

• have updated notation on the prefs in user.js - ac9f82a

@Jmkrnet thanks .. have some 🍰 or 🥧