diff --git a/releases/next/docs/images.html b/releases/next/docs/images.html index 5dcddbb891e..373de2a6d30 100644 --- a/releases/next/docs/images.html +++ b/releases/next/docs/images.html @@ -24,7 +24,8 @@ }, body: 'Your Body goes here' }} - style={{width: 400, height: 400}} />
In some cases you might only want to display an image if it is already in the local cache, i.e. a low resolution placeholder until a higher resolution is available. In other cases you do not care if the image is outdated and are willing to display an outdated image to save bandwidth. The cache source property gives you control over how the network layer interacts with the cache.
default: Use the native platforms default strategy.reload: The data for the URL will be loaded from the originating source.
+ style={{width: 400, height: 400}} />Sometimes, you might be getting encoded image data from a REST API call. You can use the 'data:' uri scheme to use these images. Same as for network resources, you will need to manually specify the dimensions of your image.
This is recommended for very small and dynamic images only, like icons in a list from a DB.
In some cases you might only want to display an image if it is already in the local cache, i.e. a low resolution placeholder until a higher resolution is available. In other cases you do not care if the image is outdated and are willing to display an outdated image to save bandwidth. The cache source property gives you control over how the network layer interacts with the cache.
default: Use the native platforms default strategy.reload: The data for the URL will be loaded from the originating source.
No existing cache data should be used to satisfy a URL load request.force-cache: The existing cached data will be used to satisfy the request,
regardless of its age or expiration date. If there is no existing data in the cache
corresponding the request, the data is loaded from the originating source.only-if-cached: The existing cache data will be used to satisfy a request, regardless of