So why is this happening? Well when you’re using fragment transitions, what actually happens to the exiting (Fragment A) and entering (Fragment B) content views is the following:
Regardless of the implementation, the transition messes with both. Fragment A uses a CoordinatorLayout and AppBarLayout, whereas Fragment B uses custom window inset handling (via an OnApplyWindowInsetsListener). The problemīoth of these fragments make heavy use of the window insets to draw behind the system bars. Anyway, you can see that we suddenly lost all status bar handling when the transition was added, and the views got pushed up behind the status bar. I did not want to overcomplicate the first post so decided to write this up separately.
Woops, not exactly what I showed in the first post 🤐.
0 kommentar(er)
