Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Image fadeDuration property

Open
#461 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
css, javascript, react-native

Research direction

Start by locating the createStrictImage entry point and read the linked react-native discussion about fadeDuration. Determine and document the intended cross-platform behavior and how an override should work without relying on the nonstandard html.img property. Done means the project has a decided, implementable approach with its expected image-loading behavior clarified.

Written by the indexing model from the issue text.

Description

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: https://github.com/facebook/react-native/issues/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)

Dominant language
JavaScript
Stars
3.6k
Forks
206
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from react/react-strict-dom

All issues in react/react-strict-dom

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.