Ovo će web mjesto raditi na ograničen način, dok obavljamo održavanje stranice. Ako neki članak ne riješi tvoj problem i ako želiš postaviti pitanje, naša zajednica za podršku spremna je pomoći na Twitteru @FirefoxSupport i na Redditu /r/firefox.

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Need a way to lock the browser down for Kiosks

  • 1 odgovor
  • 1 ima ovaj problem
  • 1 prikaz
  • Posljednji odgovor od Mkll

more options

Hello,

We have been using Firefox for several kiosk devices utilizing the mKiosk extension but now it seems our computers are starting to auto-migrate to the new Firefox Quantum. The main purpose of the mKiosk extension was to lock the browser completely down so the user could not access other pages, settings, bookmarks, etc.

With this new migration mKiosk, as well as most other extensions are no longer compatible which has completely compromised our network.

I am hoping someone knows how to completely lockdown this new Firefox using settings (advanced) or another extension. Also, is there anyway to completely halt the migration to the rest of our network so we do not have this problem at all?

This has put us in a very critical position so I would appreciate any quick assistance

Thank you!

Hello, We have been using Firefox for several kiosk devices utilizing the mKiosk extension but now it seems our computers are starting to auto-migrate to the new Firefox Quantum. The main purpose of the mKiosk extension was to lock the browser completely down so the user could not access other pages, settings, bookmarks, etc. With this new migration mKiosk, as well as most other extensions are no longer compatible which has completely compromised our network. I am hoping someone knows how to completely lockdown this new Firefox using settings (advanced) or another extension. Also, is there anyway to completely halt the migration to the rest of our network so we do not have this problem at all? This has put us in a very critical position so I would appreciate any quick assistance Thank you!

Svi odgovori (1)

more options

Hello, try running Firefox in headless mode: https://developer.mozilla.org/en-US/Firefox/Headless_mode