> The different environment name is one thing. But because we no longer
check that the name is "correct" any snap app calling a non-snap Firefox
will now cause Firefox to think it is running as a snap again.
Doh. Definitely file a bug. I'll update the patch.
--
You received this bug notification
1. Why are you setting SNAP_NAME?
2. That made it so we don't check SNAP_NAME at all (only SNAP_INSTANCE_NAME) so
I don't think it should have affected this (unless I'm reading my own code
wrong :) )
--
You received this bug notification because you are a member of Desktop
Packages, which is su
This is also affecting Amazon.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1877038
Title:
[upstream] Firefox lacks FIDO2 support with Yubikeys
Status in Mozilla Firefox:
Confirm
This doesn't happen with our new Marquee implementation.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/47751
Title:
Dos problem with marquee tag
Status in Mozilla Firefox:
Invalid
This broke LDAP autoconfig.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1854363
Title:
[upstream] ReferenceError: processLDAPValues is not defined
Status in Mozilla Thunderbir
I was only referring to the use of user.js for enterprise. I do
understand that it's worthwhile to have locking of prefs in JS file for
Firefox purposes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.laun
> Looking forward to see the patch landed as we use it at Fedora.
For what purpose? user.js shouldn't be used for anything mission
critical at all.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad
It's not the same syntax, that's my point.
pref() in a prefs.js file is NOT the same as pref() in an AutoConfig.js
file.
pref() in prefs.js sets the default pref, defaultPref() in an Autoconfig
sets a default pref.
user_pref() in prefs.js sets a user pref, pref() in an AutoConfig file
sets a use
user.js was never intended to be an enterprise level feature for
configuration of Firefox. I don't recommend using it for that.
For enterprise configuration, we have provided Autoconfig since day one,
and we are working on a better solution involving JSON, GPO and possibly
authors.
Our goal is to
(In reply to Mike Hommey (VAC: 31 Dec - 11 Jan) [:glandium] from comment #40)
> (In reply to Mike Kaply [:mkaply] from comment #39)
> > Oddly, this document:
> >
> > https://developer.mozilla.org/en-US/docs/Mozilla/Preferences/
> > A_brief_guide_to_Mozilla_preferences
> >
> > Says we already supp
You didn't address my comments.
I really don't want it being called lockPref. That will confuse it with
the autoconfig "lockPref" function.
There is already enough confusion with pref()
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fi
To expound on what :glandium said:
Extensions can lock preferences with:
Components.classes["@mozilla.org/preferences-service;1"]
.getService(Components.interfaces.nsIPrefService)
.getBranch(null)
.lockPref("name_of_pref");
Locking a preference doesn't affec
> Looking forward to see the patch landed as we use it at Fedora.
For what purpose? user.js shouldn't be used for anything mission
critical at all.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launc
user.js was never intended to be an enterprise level feature for
configuration of Firefox. I don't recommend using it for that.
For enterprise configuration, we have provided Autoconfig since day one,
and we are working on a better solution involving JSON, GPO and possibly
authors.
Our goal is to
I was only referring to the use of user.js for enterprise. I do
understand that it's worthwhile to have locking of prefs in JS file for
Firefox purposes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.
It's not the same syntax, that's my point.
pref() in a prefs.js file is NOT the same as pref() in an AutoConfig.js
file.
pref() in prefs.js sets the default pref, defaultPref() in an Autoconfig
sets a default pref.
user_pref() in prefs.js sets a user pref, pref() in an AutoConfig file
sets a use
To expound on what :glandium said:
Extensions can lock preferences with:
Components.classes["@mozilla.org/preferences-service;1"]
.getService(Components.interfaces.nsIPrefService)
.getBranch(null)
.lockPref("name_of_pref");
Locking a preference doesn't affec
You didn't address my comments.
I really don't want it being called lockPref. That will confuse it with
the autoconfig "lockPref" function.
There is already enough confusion with pref()
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to th
(In reply to Mike Hommey (VAC: 31 Dec - 11 Jan) [:glandium] from comment #40)
> (In reply to Mike Kaply [:mkaply] from comment #39)
> > Oddly, this document:
> >
> > https://developer.mozilla.org/en-US/docs/Mozilla/Preferences/
> > A_brief_guide_to_Mozilla_preferences
> >
> > Says we already supp
This is a fly by night review.
I don't think it should be "lockPref" like autoconfig. With autoconfig,
it's a function call.
With the default pref files, you're specifying a preference.
so:
locked_pref("foo", "bar")
makes more sense it that context (the same as user_pref)
Looking through the
This is a fly by night review.
I don't think it should be "lockPref" like autoconfig. With autoconfig,
it's a function call.
With the default pref files, you're specifying a preference.
so:
locked_pref("foo", "bar")
makes more sense it that context (the same as user_pref)
Looking through the
21 matches
Mail list logo
