Repository navigation
If an image is available in the tree currently, it should be resolvable by key without reloading even if it didn't fit into the image cache #49456
Description
This is slightly different from #47383
In this case, we're not concerned about the same widget re-resolving when its dependencies change, we're concerned about multiple image widgets that are actually displaying the same image, but for some reason that image did not make it into the cache (or got evicted from the cache since it was first loaded).
For example, a list that has the same image in every row and some other images as well that change. That same image should never have to be reloaded during scrolling, even if it got evicted from the cache.
/cc @ds84182 @gaaclarke
Activity
[-]If an image is available in the tree currently, it should be resolvable by key even if it didn't fit into the image cache[/-][+]If an image is available in the tree currently, it should be resolvable by key without reloading even if it didn't fit into the image cache[/+]dnfield commentedon Jan 25, 2020
Alternatiely, if you managed to resolve a really big image, and it was too big for the cache, and then you want to resolve it again at some point and it's still in tree, this would help.
dnfield commentedon Feb 4, 2020
Design doc: https://flutter.dev/go/widget-tree-image-cache
lock commentedon Apr 15, 2020
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.