mirror of
https://github.com/LiveContainer/LiveContainer.git
synced 2026-04-25 17:15:50 +03:00
[GH-ISSUE #728] [Bug/Improvement] Extended Fullscreen iPad only apps look weird on iOS. #652
Labels
No labels
bug
compatibility
enhancement
multitasking
pull-request
safe area
status: broken
status: usable
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/LiveContainer#652
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @FlipIsLickin on GitHub (Aug 4, 2025).
Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/728
Describe the bug
When completely fullscreening a ipad app, the buttons that stay stuck on the top of the screen can't be clicked on because of the notch and maybe the dynamic island. I assume it's also because of the status bar/info.
Instructions to reproduce
Any ipad, or landscape only app (force portrait), and run it in multitask. Click the fullscreen button, and then fullscreen further by closing the dock.
What version of LiveContainer and iOS are you using?
LiveContainer+SideStore 3.6.0-Release iOS 18.2
Other info
Im basically just asking if it's possible to make an option to add a blank black space where the time and battery is to push the top buttons down.
@khanhduytran0 commented on GitHub (Aug 4, 2025):
Maybe expected behavior, since collapsing the dock would hide the window bar altogether. Plus adding blank space would defeat the purpose of safe area. Please send a screenshot.
@FlipIsLickin commented on GitHub (Aug 4, 2025):
And the two middle buttons are blocked by the notch. I have a iPhone 13.
@khanhduytran0 commented on GitHub (Aug 4, 2025):
I guess you're forcing undefined behavior, is it different when running singletask?
@FlipIsLickin commented on GitHub (Aug 4, 2025):
No it's the same thing. Mistake on my part I should've tried it both ways. I think it would be easier to fix if it were in multitask, but I should've known it was the same for both.
@khanhduytran0 commented on GitHub (Aug 4, 2025):
While the gap can be easily added in multitask, it causes inconsistency when running singletask. So this should be fixed in the app side instead.