Update to API 30 and use new APIs for fullscreen/system bars #654
Conversation
Hi, I can't really test because I have several others bugs with API 30 that I will try to fix before merging your PR. |
@FredJul Ah I didn't think about that edge case 🤦♂️ my bad. The easiest solution is probably to have the FAB buton disappear when scrolling down just like the BottomNavigationView I added that to this PR (but there is a small alignment issue with the snackbar, maybe the snackbar should go at the top rather than the bottom since the bottom is kind of busy?) So yes, this PR fixes the issues you mentioned in #648 |
Great, that solution is OK for me. But now I have another issue: snackbars (like the "article is read" one) are now above the FAB and it's not pretty |
I can probably fix that, but I will need a create a custom behavior for the FAB to put the snackbars below the FAB. I can probably get a PR out for it tomorrow :) |
And for information I still have a bug where the bottom bar sometimes does not reappear (even with a scroll up). That one is a bit problematic and I'm not sure why it appears exactly. |
Actually I just found a way to reproduce: |
I'll try to debug why the bottom bar doesn't appear when relaunching the app... Might be an issue with the support library behavior and I might have to make a custom one |
I fixed the issue with the bottom bar not appearing when scrolling up, just need to figure out a good spot for the snackbar |
API 30 deprecates a ton of things including the way to do fullscreen apps underneath the status bar/navigation bar. This updates the app to work on API 30 and changes adds if/else for these new inset APIs.
Great job 👍 seems to work very well |
API 30 deprecates a ton of things including the way to do fullscreen apps underneath the status bar/navigation bar. This updates the app to work on API 30 and adds if/else for these new inset/window APIs.
Also fixes a crash when swiping is disabled on entry fragment.