Skip to content
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

[Android] Image blurRadius does not work when resizeMode is specified #16780

Closed
philipyun opened this issue Nov 10, 2017 · 1 comment
Closed
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@philipyun
Copy link

Is this a bug report?

Yes. When using the blurRadius tag on the Image component, it only works when a resizeMode is omitted. This exists only in android.

Have you read the Contributing Guidelines?

Yes

Environment

Environment:
OS: macOS Sierra 10.12.6
Node: 6.11.0
Yarn: Not Found
npm: 3.10.10
Watchman: 4.9.0
Xcode: Xcode 9.1 Build version 9B55
Android Studio: 2.3 AI-162.4069837

Packages: (wanted => installed)
react: ^16.0.0 => 16.1.0
react-native: ^0.49.3 => 0.49.5

Steps to Reproduce

  1. Make an image component
  2. Supply any source image to the component
  3. Give it a blur radius and a resize mode
  4. resize mode can be specified in either style prop or the resizeMode prop and the same issues will occur.

Expected Behavior

I should be able to specify a resize mode for dynamic fitting of an image and also have a blur filter applied to an image

Actual Behavior

The resize mode takes precedence over the blur filter and ignores any blurRadius value supplied to the image component. The screenshots below show both iOS and Android renderings using Expo's snack tool. I expect the way it works in iOS to work the same in Android.

android
ios

(Write what happened. Add screenshots!)

Reproducible Demo

A reproducible demo can found at this expo snack:

https://snack.expo.io/@philipyun/android-image-blurradius-bug

@stale
Copy link

stale bot commented Jan 9, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Jan 9, 2018
@stale stale bot closed this as completed Jan 16, 2018
@facebook facebook locked and limited conversation to collaborators May 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests

1 participant