-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Gradient fallback tints #398
Comments
I think this is more of a bug in the backwards compatibility for |
You might also be interested in #384 |
Ah yes, I just realized that! The As for |
This is a follow-up to #397, and will hopefully be solved by it, but here it is as a separate issue anyways.
My use case is this: I use a progressive blur at the top of a scrollable container, and I'd like to use a gradient where the blur isn't supported (older/lower-end Android devices).
For now,
fallbackTint
takesHazeTint
, which doesn't support taking a gradient, so I'm forced to set it toColor.Transparent
for now.This could theoretically be done by adding my own
background
modifier above or belowhazeChild
, but that's not ideal:abovebelowhazeChild
, then it's gonna be always drawn on top of the blur. Not great.belowabovehazeChild
, it's gonna interfere with the color of the blur, particularly when using amask
instead ofprogressive
.(didn't try though, I could be wrong!)I tried this and yes, withmask
it has an effect.That itself could be fixed by checking if Haze is supported, but Haze doesn't expose any way to know whether or not blur is supported on the current device. I filed an issue for that at #399.
I might be missing something very obvious, so take this with a grain of salt 😅
And thanks for the awesome library!
The text was updated successfully, but these errors were encountered: