roundingBorderColor cause the placeholder image display error
See original GitHub issue<com.facebook.drawee.view.SimpleDraweeView
android:layout_below="@id/button"
android:id="@+id/simple"
android:layout_centerHorizontal="true"
android:layout_width="match_parent"
android:layout_height="600px"
fresco:placeholderImage="@drawable/logo"
fresco:roundingBorderWidth="10px"
fresco:roundingBorderColor="@color/image_detail_help_background" />
then
- Fresco version: all version
- Platform version:all devices
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Placeholder, failure and retry images - Fresco
The failure image is displayed when a request has completed in error, either network-related (404, timeout) or image data-related (malformed image, unsupported ...
Read more >Networking - Android Mobile App Development Guide - Peruzal
Placeholders and error images are not resized and must be fairly small images. Open up your static placeholder or error images in your...
Read more >Android Fresco图片处理库用法API英文原文文档2-1 ...
Actual, placeholder, retry, and failure images can all be set in XML, using attributes like fresco:actualImageScaleType . You can also set ...
Read more >Android Fresco图片处理库用法API英文原文文档2-1(Facebook开源 ...
The most common cause of this is an invalid URI, or lack of connection to the ... Actual, placeholder, retry, and failure images...
Read more >GenericDraweeHierarchy - Fresco API
A SettableDraweeHierarchy that displays placeholder image until the actual image is set. If provided, failure image will be used in case of failure ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s both a CPU and (smaller) memory overhead yes since you tell Fresco to round the image with 0dp and draw a border, which means we need to account for that. I’ve outlined a couple alternatives above that should be (a bit) more efficient.
@zmroczek if you disable placeholder rounding, will not reproduce this issue