-
-
Notifications
You must be signed in to change notification settings - Fork 373
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
System navigation bar is not correctly rendered sometimes #2461
Comments
I just want to make sure, but I can't conclude 100% from the cropped screenshot. Do you use gestures or navigation buttons for the system navigation? If you use gestures, is your full-screen indicator shown or hidden? Just so I know which navigation mode to test at least the theme. I recently experienced a bug when I switched to a new ROM, where when I changed the wallpaper, the theme wasn't properly applied to Florisboard, and the colors were somehow mixed with the previous theme (from the previous wallpaper). However, I just exited the text field and dismissed the keyboard, then re-entered the typing field to make the keyboard reappear, and the theme applied properly. However, I thought this was a small bug in the new ROM, hm |
This bug is actually related to the fact that the system UI helpers of Google Accompanist are not actively maintained anymore and I have to get creative once again fixing the background color. The issue is that the system navigation bar (the bar with the gesture bubble or the classic 3 buttons) is system space but apps have some sort of control over it, although it is only partially documented and not the most stable system API... Ofc that doesn't mean there isn't an issue with the internal theme handling too, if colors within the keyboard area are messed up for instance. |
Yes I am using gestures on my device.
…On Sat, 27 Apr 2024, 5:49 pm itsmarta, ***@***.***> wrote:
I just wan't to make sure, but I can't conclude 100% from the cropped
screenshot. Do you use gestures or navigation buttons for navigation? If
you use gestures, is your full-screen indicator shown or hidden? Just so I
know which navigation mode to test at least the theme.
Even the color of the submit button stands out a bit, as if the theme
didn't apply properly. Also, have you noticed if this happens immediately
after changing the wallpaper, or randomly?
I recently experienced a bug when I switched to a new ROM, where when I
changed the wallpaper, the theme wasn't properly applied to Florisboard,
and the colors were somehow mixed with the previous theme (from the
previous wallpaper). However, I just exited the text field and dismissed
the keyboard, then re-entered the typing field to make the keyboard
reappear, and the theme applied properly. However, I thought this was a
small bug in the new ROM, hm
—
Reply to this email directly, view it on GitHub
<#2461 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARXSGV7NTT2XBM4ZFURRYZDY7OJUNAVCNFSM6AAAAABG37NA52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBQGUZDAMBQGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I get that it’s tough with the Google Accompanist system UI helpers not being maintained anymore. It sounds like a real challenge to come up with creative fixes for the background color issue. Your efforts to sort this out despite those hurdles are really appreciated, Patrick 🥹
I checked the internal theme handling and found a small "issue". When changing the theme while the keyboard is open, some material you colors from the previous wallpaper, mix with the new wallpaper's colors. However, closing and opening the keyboard fixes the issue. So, not a big deal I guess |
Short description
Sometime the space below the keyboard shows different color look like it is background color which match with homescreen wallpaper. But sometime the color is same as keyboard material color.
See image attached
Steps to reproduce
FlorisBoard Version
0.4.0 beta 2
Install Source
GitHub
Device
realme gt neo 2
Android
Android 13
The text was updated successfully, but these errors were encountered: