feat: add game back menu

[dos-ise]

feat: add in‑stream back menu for Tizen

Adds a simple back‑menu overlay when pressing Back during a stream on Tizen.

The menu helps avoid accidental disconnections and provides quick access to key events (ESC, F11, etc.) that Tizen remotes cannot send directly. Useful for navigating game menus or exiting fullscreen modes.

similar to this menu avaiable on android tv
moonlight-stream/moonlight-android#1171

Highlights

• Back‑press opens a small, remote‑friendly menu
• Buttons for ESC, F11, and other common PC keys
• Confirmation before disconnecting
• Lightweight overlay that doesn’t interrupt streaming
• Fully navigable via D‑pad and OK/Back

Screenshots

[brightcraft]

Hi @dos-ise, sorry for the late reply, and thanks for submitting this PR for the in-stream dialog — it’s a useful feature, and I can see the potential here! I haven’t had time to test it yet, but here’s some initial feedback:

• Dialog creation – Currently the dialog is created via static HTML. It should be created dynamically via jQuery, similar to the Host Menu, for consistency and maintainability.
• Dialog title – I suggest renaming it to “Stream Menu”. The current title, may be confusing, since in the future we might use that name for per-game dialogs like Host Menu does for hosts.
• Dialog button – The “Disconnect” button is redundant, as it duplicates the existing Quit Session functionality, so it can be removed (unless you want to assign a new functionality to it later).
• Trigger key – Based on your changes, pressing RETURN on the remote currently opens the dialog. On the Tizen platform, ESC on the keyboard is equivalent to RETURN on the remote. Keyboard users expect ESC to send an escape key event, so opening the dialog on RETURN/ESC causes unexpected behavior for them. We should choose a different key that doesn’t conflict with ESC (possibly the GREEN color button on the remote) and revert the workaround to ensure the ESC key continues to function normally.
• Input support – Currently the menu is accessible via remote and keyboard, but not via gamepad. Should the dialog also be accessible via gamepad, or is it intended to remain remote only?

Once these adjustments are made, I’ll be happy to test and consider merging. I can also help with improvements if needed, but I’m currently busy working on the navigation part of the app to ensure compatibility across all Tizen OS versions and fixing some existing bugs.

[dos-ise]

Thanks for the feedback! Just to clarify the intention behind the menu: the goal is to offer a more intuitive, console‑like experience similar to Xbox Cloud Gaming or Luna on Samsung TV.

Using the BACK button is essential for that — it’s the only button that’s always visible, easy to reach, and universally understood by users.

On newer Samsung remotes, the color buttons are hidden and hard to access, and users have no idea what each color is mapped to. If we move the menu to a color key, we lose the whole point of making the UI more intuitive.

About ESC vs BACK:
Is there really no way to distinguish them? ESC on a keyboard and BACK on a remote should have different keycodes. If Tizen merges them, maybe there’s still a way to differentiate through event.code, event.key, or device metadata. If we can separate them, ESC can behave normally for keyboard users while BACK opens the menu on remotes.

If that’s possible, we can keep the UX consistent without breaking keyboard behavior.

Gamepad support would definitely be great — the more consistent the experience across input devices, the better. The only question is whether we actually have any usable key combinations left. Most common buttons are already mapped for gameplay, so unless there’s a spare combo we can safely use without interfering with games, adding gamepad access might be tricky.

You are correct “Disconnect” button is redundant at the moment should separated to close the current app.

[brightcraft]

Thanks for the clarification, I understand the UX goal, and I agree that using BACK feels natural and console-like.

The concern is mainly technical. On the Tizen platform, ESC (keyboard) and RETURN/BACK (remote) are likely mapped at the system level, so there’s a high chance they behave identically inside the app. If that’s the case, distinguishing them reliably may not be possible.

That said, we should at least test whether they can be separated via event.code or event.key. If we can reliably distinguish them across Tizen versions, keeping BACK would be ideal. If not, we’ll need a different trigger to avoid breaking keyboard ESC behavior. A possible alternative could be the MediaPlayPause key (since it’s accessible and near Smart Hub on most TV remotes), but we can decide that after testing.

At the moment, I can’t properly check this since I’m focused on navigation improvements and cross-version compatibility, but I’ll revisit and test it when I have time.