Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Full-Screen Layout Padding Issue with 'hasStatusBar' Flag #119

Closed
3 tasks done
zeoowl-dev opened this issue Oct 3, 2023 · 0 comments · Fixed by #128
Closed
3 tasks done

[Bug]: Full-Screen Layout Padding Issue with 'hasStatusBar' Flag #119

zeoowl-dev opened this issue Oct 3, 2023 · 0 comments · Fixed by #128
Assignees
Labels
@bug Something isn't working @priority-critical @UI
Milestone

Comments

@zeoowl-dev
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Is there a StackOverflow question about this issue?

  • I have searched StackOverflow

What happened?

The FullScreenLayoutBase method in the dev.teogor.ceres.screen.core.layout package provides a convenient way to create full-screen layouts in Jetpack Compose applications. However, it seems that when the hasStatusBar parameter is set to true, the status bar padding is not being added as expected.

Steps to Reproduce:

  1. Use the FullScreenLayoutBase composable with the hasStatusBar parameter set to true.
  2. Observe that the status bar padding is not added to the layout.

Expected Behavior:
When hasStatusBar is set to true, the FullScreenLayoutBase should add the necessary status bar padding to ensure content is not obscured by the status bar.

Actual Behavior:
The status bar padding is not being added when hasStatusBar is set to true, which may lead to content being obscured by the status bar.

Relevant logcat output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@teogor teogor self-assigned this Oct 3, 2023
@teogor teogor added @bug Something isn't working @UI @priority-critical labels Oct 3, 2023
@teogor teogor added this to the 1.0.0-alpha03 milestone Oct 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@bug Something isn't working @priority-critical @UI
Projects
Development

Successfully merging a pull request may close this issue.

2 participants