Weston Kiosk Shell chromium losing focus upon sad tab kill

Hello,

Working on a project which is launching a Weston Kisok Shell for a single chromium kiosk targeting a localhost webserver, running on imx8.

We are encountering an issue when chromium kills a "sad_tab". Seems as though this kills and restarts the tab in the event of memory issues within chromium. When this happens, we lose focus on the chromium window and are no longer able to navigate with the keypad input setup for the kiosk.

Here is our config weston ini:

[core]
shell=kiosk-shell.so
idle-time=0
useg2d=0
xwayland=false
#use-g2d=1

[output]
name=HDMI-A-1
app-ids=chromium-browser (/home/root/.config/)
mode=71.00 1280 1328 1360 1440 800 803 809 823 +hsync +vsync

I thought adding the app id as capture from our chromium launch command would stop the focus from changing but it did not. I need to find a way to prevent the focus from leaving. We are able to restore focus by clicking but that is only because this is in the lab on a test machine with a keyboard/mouse hooked up, the real setup will only have a small keypad.

WAYLAND_DEBUG=1 chromium 2>&1 \
    --no-sandbox \
    --window-size=1920,1080 \
    --start-fullscreen \
    --kiosk \
    --incognito \
    --noerrdialogs \
    --disable-translate \
    --no-first-run \
    --fast \
    --fast-start \
    --disable-infobars \
    --disable-features=TranslateUI \
    --disk-cache-dir=/dev/null  \
    --password-store=basic \
    --in-process-gpu \
    --touch-events \
    --user-data-dir=/home/root/.config/ \
    --disable-web-security \
    http://127.0.0.1 | grep app

[4088792.203]  -> xdg_toplevel@36.set_app_id("chromium-browser (/home/root/.config/)")

Any tips, tricks or advice you could give would be greatly appreciated.

Thanks