react-native has an android only property fadeDuration that adds a fade-in effect to images while they load.
This is set by default to 300ms leading to an unexpected inconsistency across platforms.
the issue was discussed here: react/react-native#10194
where was decided to add a prop to control it, but not removing the default value to avoid breaking changes.
I'm wondering what is the position on the topic from the react-strict-dom POV. Should the createStrictImage force it to 0 and let the optional animation be handled by css transition polyfills?
If not, how can the behavior be overridden? In react-native the fadeDuration property can be used to reset to 0 when needed, but not being a valid web API is not allowed in html.img (as well as possibly creating conflicts with transitions and/or animations)
react-native has an android only property
fadeDurationthat adds a fade-in effect to images while they load.This is set by default to
300msleading to an unexpected inconsistency across platforms.the issue was discussed here: react/react-native#10194
where was decided to add a prop to control it, but not removing the default value to avoid breaking changes.
I'm wondering what is the position on the topic from the react-strict-dom POV. Should the
createStrictImageforce it to0and let the optional animation be handled by css transition polyfills?If not, how can the behavior be overridden? In react-native the fadeDuration property can be used to reset to 0 when needed, but not being a valid web API is not allowed in
html.img(as well as possibly creating conflicts with transitions and/or animations)