4 ms·
It can be even easier by just autostarting: iceweasel "https://www.google.com" ...and installing something like https://addons.mozilla.org/en-us/firefox/a
by r3bl 10y ago
It can be even easier by just autostarting:
iceweasel "https://www.google.com"
...and installing something like https://addons.mozilla.org/en-us/firefox/addon/r-kiosk/ https://addons.mozilla.org/en-us/firefox/addon/r-kiosk/
Or, you can take advantage of this almost two years old bug related to full screen mode: https://bugzilla.mozilla.org/show_bug.cgi?id=1049807 https://bugzilla.mozilla.org/show_bug.cgi?id=1049807
It takes ~1 minute for my RPi2 to boot and start IceWeasel, but it gets the job done in the quickest way possible.
- punjabisingh 10y agoThat's the setup I have running. Instead of r-kiosk, I've been using mKiosk, which is a more configurable add-on: https://addons.mozilla.org/en-us/firefox/addon/mkiosk/ https://addons.mozilla.org/en-us/firefox/addon/mkiosk/
- CommanderData 10y agoWorks well, Iceweasel has better HTML5 support on the Pi than Chromium. Though struggled getting Iceweasel to start in full screen from command line, afaik there no flags, one way was to close in fullscreen state or install a plugin. Further IW shows first run dialogs. Annoying if your deploying several Pis, then theres the cursor which unclutter package helps to solve. Lastly matchbox x uses less ram than LXDE which was important in my use case. Chromium is better if you want to seamlessly deploy Pi's without spending too much time configuring them, theres a trade off somewhere - the official Chromiums package is old and IW is newer with less API. You may want to consider wrapping your command inside the while loop in the script above. I added did this after I experienced IW and Chromiums unexpectedly closing sometimes. Helped alot.