Rémi Marseault

What you call "full screen mode" is actually a [PWA (Progressive Web App)](https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps). I remember someone mentioning that PWA were acting strangely with this dynamic island. Looking at the docs...

Does this happen in all pages or only some of them? This is most likely due to using "fixed layouts" in some pages, where only a portion of the page...

A new OLED theme seems to be the best way to handle this case, feel free to create a new dark theme that suits your expectations and submit a PR...

> I've never coded in JS before Don't worry about that, you'll just have to change some JSON values. Everything else is reloaded automatically! > I did some digging into...

I also have this bug in dev mode but haven't found any trace in a release. It usually happens when you reuse an existing session, which has cached information. Opening...

Tried to reproduce and even in dev mode I didn't succeed. It must be some kind of weird edge case that only happens in unexpected scenario.

I just did some further tests, and it looks like the toast lib we use doesn't handle a very specific case, where the promise (qbit response) resolves before the toast...

> It will disappear after closing the page and opening it in a new tab though. This is weird because we store nothing in the session that would keep that...

It is possible but requires connecting to USB and launching ADB and stuff. I agree it's really not convenient. What I'm trying to understand is how the toast can appear...

Backend ping is to be expected, it's to detect whether [vuetorrent-backend](https://github.com/VueTorrent/vuetorrent-backend) is installed or not, to prevent sending useless requests after this one. However if the login page disappears after...