FooIbar

I believe it can be retrieved from [getMaximumBitmapHeight()](https://developer.android.com/reference/android/graphics/Canvas#getMaximumBitmapHeight()) on a hardware canvas or [EGL configurations](https://stackoverflow.com/a/26823209). I think it's fine to leave it to the user.

> Content is blurred all the time. Interesting, I can't reproduce it. I suspect it's related to https://android-review.googlesource.com/3017366.

https://github.com/Ehviewer-Overhauled/Ehviewer/issues/535

#692 might solve this if you wanna try.

No longer valid. @asuka-mio

It's due to `NavigationBar` started to use the new `SurfaceContainer` roles since [1.3.0-alpha02](https://developer.android.com/jetpack/androidx/releases/compose-material3#1.3.0-alpha02). So it won't get fixed until someone updates those color schemes.

Being able to support other storage locations is just a feature of SAF, which has to be used due to [scoped storage](https://source.android.com/docs/core/storage/scoped). And those file operations are IPC calls rather...

https://github.com/tachiyomiorg/UniFile/pull/2 is definitely a good improvement, but do you have benchmark results of that vs lifting `listFiles`? I'm a bit concerned because `TreeDocumentFile.exists` is also somewhat expensive. As I said...

Nice! That looks promising. I have a POC of running `findChapterDir` in parallel, would you mind testing #731 on top of the `findFile` optimization?

Compose does not support it until [1.7.0-alpha06](https://developer.android.com/jetpack/androidx/releases/compose-foundation#1.7.0-alpha06).