Status Update
Comments
ro...@gmail.com <ro...@gmail.com> #2
Hi samsadch,
In the AndroidX PDF library, the search view is animated using the
Without this, the callback might be consumed at an upper level, preventing it from being received by the PdfViewerFragment's container.
vp...@gmail.com <vp...@gmail.com> #3
Actually the search view is coming but the issue is that it is showing below the Keyboard
bh...@google.com <bh...@google.com>
gu...@google.com <gu...@google.com> #4
Still there
gu...@google.com <gu...@google.com>
m....@anfe.ma <m....@anfe.ma> #5
Hey Samsad,
It seems your concern is that the search view remains behind the keyboard when it's open, instead of being positioned below it.
As mentioned in my earlier comment
For reference, you can see the search view translation logic
To resolve this, please ensure that the view hierarchy containing the PdfViewerFragment allows insets to propagate down the view hierarchy.
Description
Expected behavior: The library should support a minimum SDK version lower than 35, allowing for broader adoption in existing projects with older Android versions.
Actual behavior: Currently, the androidx.pdf library requires a minimum SDK of 35, which limits its integration into projects targeting lower SDK versions.
Steps to reproduce:
• Add the androidx.pdf library to any project with a minimum SDK lower than 35.
• Attempt to compile the project.
Additional information:
I understand that it is common to initially release alpha versions of libraries targeting the latest SDKs. However, is there any information or plan regarding the minimum SDK version that will be supported in future releases? It would be highly beneficial for many existing projects if this library could support lower API levels, considering the potential adoption for a wider range of Android versions.