Overscan/Border after upgrading browser block and adding FLAGS

terehov commented 2 years ago

This block works like charm and helps a lot, and is even probably the main reason we use Balena Cloud for our fleet of self-ordering kiosks. Since our last update a strange black border around the screen appears, as soon as we add FLAGS, and it doesn't matter which ones. As soon as I add chromium flags, this black border appears.

Old set up:

Raspberry Pi 4
balenaOS 2.75.0+rev1
Can't determin block version from few months ago
Deploy and Config through Balena Cloud
BALENA_HOST_CONFIG_disable_overscan=1

New set up:

Raspberry Pi 4
balenaOS 2.88.5+rev1
current block version
Deploy and Config through Balena Cloud
BALENA_HOST_CONFIG_disable_overscan=1

Current FLAGS: --kiosk --enable-auto-reload --app-auto-launched --enable-consumer-kiosk --noerrdialogs --disable-infobars --autoplay-policy=no-user-gesture-required --disable-session-crashed-bubble --no-first-run --disable-pinch --overscroll-history-navigation=0

overflow

mv3 commented 2 years ago

Try setting window-size and window-position flags: --window-size=1920,1080 --window-position=0,0

phil-d-wilson commented 2 years ago

Thanks @mv3 !!

Glad you're getting good use out of the block @terehov Using the FLAGS variable basically overrides any of the other settings, since they almost all pass in flags to the command that runs chromium. When you use the FLAGS variable, you're basically saying you'll specify all the flags you want/need.

terehov commented 2 years ago

That's good to know. I believe previous versions worked a bit differently since I just ran into this problem after an update. Anyways, thank you very much @mv3 and @phil-d-wilson, it works now 👍

balena-io-experimental / browser

Overscan/Border after upgrading browser block and adding FLAGS #105