rsnext/test/integration/next-image-new/default
Steven 73b552a9a5
fix(next/image): undo tight coupling between priority=true and fetchPriority=high (#67351)
## History

When we added `priority` prop to `next/image`, there was no
`fetchPriority` so we instead used this to preload the image in the
head.

Then when browsers added support `fetchPriority`, we automatically added
`fetchPriority=high` when `priority={true}` to signal to the browser
that this was a high priority image. This priority is added to the img
and the preload.

However, we saw cases where images are blocking critical css. Per
@gnoff:

> React currently prioritizes font preloads then high priority images,
then css in the initial page load

Due to these changes in React (aka Float), we should no longer set
`fetchPriority=high`, although the user can still manually add that prop
if needed.
2024-07-01 14:42:42 -04:00
..
components Fix image emittion for pure client image (#44831) 2023-01-12 11:24:59 -08:00
pages fix(next/image)!: error when src has leading or trailing space (#65637) 2024-05-14 18:00:27 +00:00
public Add unstable_getImgProps export from next/image (#51205) 2023-06-29 01:35:08 +00:00
test fix(next/image): undo tight coupling between priority=true and fetchPriority=high (#67351) 2024-07-01 14:42:42 -04:00
style.module.css BREAKING CHANGE: Rename next/image to next/legacy/image & rename next/future/image to next/image (#41399) 2022-10-14 01:59:22 +00:00