Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Access to about:debugging while blocking all extensions via GPO

  • 3 wotmołwy
  • 1 ma tutón problem
  • 1 napohlad
  • Poslednja wotmołwa wot Dom Langella

more options

Hello,

As the title mentions, applying a block to all extensions via "*" by utilizing Extension Management GPO will block about:debugging.

Is there a way to simultaneously have all extensions blocked and about:debugging available?

Here's the JSON - { "*": { "installation_mode": "blocked" } }


Appreciate your time and help, - Dom

Hello, As the title mentions, applying a block to all extensions via "*" by utilizing Extension Management GPO will block about:debugging. Is there a way to simultaneously have all extensions blocked and about:debugging available? Here's the JSON - { "*": { "installation_mode": "blocked" } } Appreciate your time and help, - Dom

Wšě wotmołwy (3)

more options

The reason we block about:debugging is because a user can explicitly load an addon on the about:debugging.

You're right, though, that this is probably a little heavy handed. Maybe I should just disable the "load temporary addon" button.

more options

Wubrane rozrisanje

more options

Thanks for the insight and feedback!