You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In particular, notice that transitionProperty now has three list items, but transitionTimingFunction still has two.
If we applied this style object to a DOM node, ease would apply to -webkit-transform, step-end to transform, and no timing function would be applied to opacity.
Oh wow, I didn't know about that! CSS I love you.
I'm not sure how to fix this dynamically, but I will try to find some time to debug it. Any help would be highly appreciated!
RNW is only using the static prefixer, might be easier to fix there first. It looks like not all the properties are being prefixed. If there's a MozTransitionProperty there should be a MozTransitionTimingFunction. At that point you should be able to check whether the transition properties are on the object, and if the transitionProperty value needs prefixed values (like when transform is included), you can create new transitionTimingFunction values to match.
Background: In plain CSS,
transition-property
andtransition-timing-function
are interdependent.function-1
applies toproperty-1
,function-2
toproperty-2
,function-3
toproperty-3
.This is interdependence is not respected by
inline-style-prefixer
.Consider the following code:
Expectation:
ease
applies to thetransform
transition,step-end
applies toopacity
Reality: In this above block of code, the stdout is
In particular, notice that
transitionProperty
now has three list items, buttransitionTimingFunction
still has two.If we applied this style object to a DOM node,
ease
would apply to-webkit-transform
,step-end
totransform
, and no timing function would be applied toopacity
.This bug was surfaced in necolas/react-native-web#852
The text was updated successfully, but these errors were encountered: