-
Notifications
You must be signed in to change notification settings - Fork 6
fix/android crash fragment #11
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
Conversation
m-abs
commented
Jun 13, 2025
- feat: moved into a wrapper fragment class
- new fragmenet is now used
- fix: fragment init must be without arguments
ddfreiling
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code LGTM, need to test.
| return false; | ||
| } | ||
| // Checks also that the locator also contains `active` class. | ||
| // TODO: This doesn't do what we expect, if the range is visible but not active, this function will return false. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We actually fixed this on the lyt4 branch, we need to backport it here.
…er_readium into fix/android-crash-fragment
Not pretty but better
ddfreiling
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome job 🚀
Minor readability comment.
| it.locator = initialLocator | ||
| it.preferences = initialPreferences | ||
|
|
||
| it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This use of let hurts readability.