-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Error when box-shadow is set no none #10403
Comments
Did this value apply without problems in prior versions? |
Thanks @CatchABus yep see what it is, we'll include in a patch. |
Has this fix been published? :) EDIT I see that it's part of 8.6.1, however it does not seem to work for me, my app still crashes until I remove the box-shadow: none; from the respective elements which has it. |
That sounds odd - your lock file reflects 8.6+? |
Yes indeed. From the lock file:
I do a clean install with I worked around it by only using |
I confirmed this. It seems latest fix does not help with box shadow as there are few cases in core that still rely on shadow being |
Lets reopen this and get a proper patch published, thanks for bringing this up. |
@asharghi @CatchABus I tried to repro this and see no errors? All render properly and with no shadow. <Button style="box-shadow: none" />
<Button boxShadow="none" />
<Button class="none" />
.none {
box-shadow: none;
} |
Shadow should actually throw on android specifically. On iOS, it will not throw any errors but will attempt to create CALayers for shadow while not needed instead. I found few locations affected by These cases rely on box shadow or text shadow being null when |
Ok thanks that makes sense now. We'll fix android to be ignored as well in this case. |
Issue Description
After updating to core 8.6, I get this error. Seems to work with box-shadow: none anyway, but the error should be removed
Reproduction
Add an element with box-shadow: none in css or inline style
Relevant log output (if applicable)
No response
Environment
Please accept these terms
The text was updated successfully, but these errors were encountered: