[Feature Request]: Add identifier for when app is in fullscreen

[kommunarr]

Guidelines

• I have searched the issue tracker for open and closed issues that are similar to the feature request I want to file, without success.
• I have searched the documentation for information that matches the description of the feature request I want to file, without success.
• This issue contains only one feature request.

Problem Description

FreeTube gets a lot of issue reports by users who do not know that they have fullscreen mode on and/or do not know how to exit it. This is referring to the whole app — not a video — being open in fullscreen.

Proposed Solution

Add some kind of identifier to the user experience that fullscreen is on and can be disabled. E.g., a toggle in Theme Settings to enable/disable fullscreen.

Alternatives Considered

I'm not familiar with how other apps have handled this problem, but there could be other good solutions to this. If anyone does have a better idea in mind that another app employs, please share it.

Issue Labels

ease of use improvement, improvement to existing feature

Additional Information

No response

[efb4f5ff-1298-471a-8973-3d47447115dc]

IMO i dont think that adding this is worth the hassle. The cause of this are #4534 and #3220. To users that are opening reports its kind of random yes (on top of that they failed to look at already open bug reports) but if we address these issues in #5138 then we dont even need to communicate this.

[kommunarr]

I agree with those appearing to be two major causes, although people who have entered fullscreen through those bugs may not ever know it is a controllable/leaveable state even after we fix the original bugs, and people may occasionally press F11 and land up in the same place of confusion. Maybe #2822 is a little closer to it if they can figure out that a keyboard shortcut could fix it.

[efb4f5ff-1298-471a-8973-3d47447115dc]

although people who have entered fullscreen through those bugs may not ever know it is a controllable/leaveable state even after we fix the original bugs, and people may occasionally press F11 and land up in the same place of confusion

I agree.

Maybe #2822 is a little closer to it if they can figure out that a keyboard shortcut could fix it.

Hmm not sure because we need to make people aware that this exists. The way we did it before is through our documentation but only few users are reading that. If people did read our documentation then they would also know that f11` would solve their issue. So i think this sits kinda in the same realm.

[kommunarr]

You're very right, but to be fair to the users, it is inconvenient to expect people to read documentation for every problem, or even know how to find the documentation link easily. The ideal for apps is that you teach your users how to use them. With regards to this discussion, that might look like:

• Adding a Help section to the browser container that has a link to the documentation
• Adding a link to the documentation somewhere on the Settings page (where most people go to first for their regular "what's going on here" inquiries) too, and/or even linking to certain sections of our documentation for different settings
• Having app fullscreen be a configurable Theme Setting instead of just a keyboard shortcut