Image shows blank/disappears between blur placeholder and final image in Firefox (next/image with placeholder="blur") for v13.1.2

[bennettdams]

Verify canary release

• I verified that the issue exists in Next.js canary release

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Fri Apr 2 22:23:49 UTC 2021
Binaries:
  Node: 16.14.2
  npm: 8.5.0
  Yarn: 1.22.15
  pnpm: N/A
Relevant packages:
  next: 12.1.7-canary.3
  react: 18.0.0
  react-dom: 18.0.0

What browser are you using? (if relevant)

Firefox 99.0.1 (64-bit)

Describe the Bug

When using Firefox, next/image and placeholder="blur", the transition between a blur placeholder and the final image shows blank space in between. The blur placeholder just disappears before the final image is there.

This was first mentioned in this issue:
#30128 (comment)

..and supposed to be fixed in v12.1.5:
#35889

..but even with version 12.1.7-canary.3, the issue remains.

blurred image -> blank -> final image

Expected Behavior

The placeholder keeps being visible until the final image is shown.
This is only an issue in Firefox - Chrome doesn't show this blank space between the placeholder and the final image.

To Reproduce

Deployed at: https://nextjs-image-bug.vercel.app/

Here is a reproduction repo, it just uses an image from Imgur.com and a static blur URL.

• Firefox 99.0.1 (64-bit)
• Next.js 12.1.7-canary.3

1. npx create-next-app@latest --ts --use-npm .
2. Add a remote image
3. Open the browser and disable cache and throttle the network speed
4. npm run build && npm run start

[juniorbotelho]

It seems to be the normal behavior of virtual dom.

[bennettdams]

It seems to be the normal behavior of virtual dom.

I don't really get your point - as described in the issue, this does not happen in Chrome, only in Firefox, so it probably has nothing to do with the virtual DOM.

[iamfaycal]

I'm also having this issue in Firefox (It's working fine in Chrome)

Using next 12.1.5

[github-actions]

Please verify that your issue can be recreated with next@canary.

Why was this issue marked with the please verify canary label?

We noticed the provided reproduction was using an older version of Next.js, instead of canary.

The canary version of Next.js ships daily and includes all features and fixes that have not been released to the stable version yet. You can think of canary as a public beta. Some issues may already be fixed in the canary version, so please verify that your issue reproduces by running npm install next@canary and test it in your project, using your reproduction steps.

If the issue does not reproduce with the canary version, then it has already been fixed and this issue can be closed.

How can I quickly verify if my issue has been fixed in canary?

The safest way is to install next@canary in your project and test it, but you can also search through closed Next.js issues for duplicates or check the Next.js releases. You can also use the GitHub template (preferred), or the CodeSandbox or StackBlitz templates to create a reproduction with canary from scratch.

My issue has been open for a long time, why do I need to verify canary now?

Next.js does not backport bug fixes to older versions of Next.js. Instead, we are trying to introduce only a minimal amount of breaking changes between major releases.

What happens if I don't verify against the canary version of Next.js?

An issue with the please verify canary that receives no meaningful activity (e.g. new comments that acknowledge verification against canary) will be automatically closed and locked after 30 days.

If your issue has not been resolved in that time and it has been closed/locked, please open a new issue, with the required reproduction, using next@canary.

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps. Furthermore, you can upvote the issue using the 👍 reaction on the topmost comment (please do not comment "I have the same issue" without repro steps). Then, we can sort issues by votes to prioritize.

I think my reproduction is good enough, why aren't you looking into it quicker?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

• How to Contribute to Open Source (Next.js)
• How to create a Minimal, Complete, and Verifiable example
• Reporting a Next.js bug
• Next.js Triaging issues

[bennettdams]

I upgraded my reproduction repo to Next.js v13.1.2 (newest version). The steps to reproduce remain the same.

The full white placeholder as described initially is gone for this version, but there's a new behavior: The image is loaded in chunks and shows a white background in the meantime.

Not sure if this is expected, maybe this is the default browser behavior?

[balazsorban44]

This issue has been automatically closed because it wasn't verified against next@canary. If you think it was closed by accident, please leave a comment. If you are running into a similar issue, please open a new issue with a reproduction. Thank you.

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.