Project

General

Profile

Actions

Feature #1073

closed

Add an option to display under camera cutouts in full screen browsing mode

Added by v ... 10 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Next Release
Start date:
08/23/2023
Due date:
% Done:

0%

Estimated time:

Description

Would it be possible to use the little space left behind when status bar is disappearing ? Currently, this space is not used. Don't know if that's the case for all Android versions.

According to the following page, it should be possible (for, at least, Android 10).

https://stackoverflow.com/questions/72179274/hide-status-bar-in-android-10-api-29-and-use-its-space-in-the-application

Actions #1

Updated by v ... 10 months ago

  • Subject changed from Full screen mode is not using the status bar's space to Full screen mode is not using the status bar's vertical space
Actions #2

Updated by Soren Stoutner 10 months ago

Does the device you are using have a camera cutout?

Actions #3

Updated by Soren Stoutner 10 months ago

  • Subject changed from Full screen mode is not using the status bar's vertical space to Add an option to display under camera cutouts in full screen browsing mode
Actions #4

Updated by v ... 10 months ago

Yes, it has.

Actions #5

Updated by Soren Stoutner 10 months ago

I should be able to create an option to draw the full screen browsing under the cutout (some video playing apps do this, so I know it is possible). However, there should be an option to turn this off as it could cover an important aspect of a website. The question now is if the default should be enabled or disabled.

Actions #6

Updated by v ... 10 months ago

Having this option turned off by default seems, for me, to be the less annoying for most of the users. It will prevent that some users, maybe the less experienced, could think it is a bug (that some [important] part of a web page is hidden).

Actions #7

Updated by ask low 10 months ago

I believe that the cutout of the camera orb is very small, whether you take even a small device or a flagship. The odds of it interfering the website's interface should be almost negligible because most of the websites contain headers, with some title / heading. You can easily the guess the missing text there, as the orb cuts only a single letter.

Even if the website hides the header while scrolling (through scripting), that wouldn't be an issue too. Caz the screen real estate is too large to even begin with, users can scroll the content where the camera orb doesn't exist.

And in the rare cases, the orb isn't an orb. Maybe it's a notch. But the devices that were launched with a notch, were very less. So you might factor in the notch area coverage setting. But nonethless of the defaults on or off, I would say bringing this config out into the userspace will be a very good move.

Actions #8

Updated by Soren Stoutner 7 months ago

  • Priority changed from 3.x to Next Release
Actions #10

Updated by ask low 5 months ago

How do you manage issue priorities that are "Next Release" which were of closed status ?
Wouldn't this cause confusions for you on writing the changelogs of the next release ?

Actions #11

Updated by Soren Stoutner 5 months ago

I'm not sure I understand your question, but closing features when they are implemented helps when it comes to preparing the changelog.

Actions #12

Updated by ask low 5 months ago

Of course but just wondering how you'd track those, as they get mingled into the older issues which were closed & their statuses still remaining as "Next release" like this one.
Why not change the Priority to "3.x" since these are done?

Actions #13

Updated by Soren Stoutner 5 months ago

I sort all closed issues by date. Then I start at the release date of the last version and read forward through each issue, seeing if it contains anything that should be in the changelog.

Actions

Also available in: Atom PDF