feat(tauri): implement fullscreen toggle functionality

[seanmcbroom]

Added fullscreen toggle feature using Tauri's window API. Permissions for fullscreen have also been updated in the tauri.conf.json file.

[jellyfin-bot]

Cloudflare Pages deployment

Latest commit	61f1a3a
Status	✅ Deployed!
Preview URL	https://9cd3bda7.jf-vue.pages.dev
Preview alias	https://tauri-fullscreen.jf-vue.pages.dev
Type	🔀 Preview

View build logs

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ferferga]

I'm labeling this as blocked because of: #2002

Now that I'm dividing the project more and more in a monorepo (see packages folder), my idea was at some point to have a tauri-runtime package that contains all tauri-related specific logic, so we don't "pollute" the main codebase with code that doesn't belong to the standard DOM environment (improving maintenance and reducing bundle size along the way).

For this concrete example, I think it would be far easier than the skip intro plugin.
I think it would be a matter of creating that tauri-runtime package in packages folder and then make the main.ts and index.html of @jellyfin-vue/frontend exportable in their package.json, so you can import them in the entrypoint of the tauri-runtime package. Then, in that entrypoint, set an event handler that listens for window's fullscreen events and has Tauri's fullscreen method as its callback.

This is the overall high-level idea of how I think it would work, do you wanna try to tackle it?

[seanmcbroom]

I understand. It sounds like a significant amount of work for the small change I’m proposing. Perhaps it makes sense to open a new PR to lay the groundwork for adding functionality like this in the future..

On another note, I noticed there hasn’t been an official Tauri build released in over a year. Do you think this is something that will see more support in the future? Personally, I find it loads much faster than the web version since most assets are requested locally. Plus, as this is an alternative client, I imagine most users would prefer running it locally rather than hosting it.