add full size preview & fix fc on Android 12L and 13 #144
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, thanks for your contribution, I'll check that ... |
|
Just downloaded and tested 2.0.2-beta. Seems that local caching works very good now and very good speed enhancement overall. Full Size pictures works. Very well development. Thanks a lot for your effort and keep going :-) |
|
That's good to hear 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The PR allows user to view the full (original) size of images on preview.
Note that cookies should be included when getting images, to be compatible with original_url_protection.
The PR also fixes a FC on some Android 12L and Android 13 ROM. Reference: https://stackoverflow.com/questions/74163927/flutter-chrash-in-android-12l-with-no-interface-method-addwindowlayoutinfoliste
The FC is related to androidx.window:window and it is fixed in 1.1.0-alpha04. Because it is an alpha version, the stable version 1.0.0 is used instead, which also does not have the problem.