Conversation
This was referenced Sep 12, 2026
Member
Author
|
Superseded by #500, which now carries the whole change against main. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Ordinary image attributes disappeared between the Server Component snapshot and the picture renderer. In particular, accepted JSX accessibility attributes could silently lose their description relationship. Invalid loading combinations also compiled, and lazy automatic sizing never activated on the image.
Changes
100vwfor omitted width-descriptor source sizes. Putsizes="auto"on lazy images requesting automatic sizing, leave fallback lengths on sources, and reject eager automatic sizing.Verification
yarn workspace @transloadit/img check(73 tests plus type fixtures).yarn test:img:fixture: packed-package production Next build, safe prerendering, request-time signing, authorized redirects, tampering and secret exclusion.git diff --check.This is PR A of the agreed four-PR iteration. No signing policy/default lifetime changes, publication or production access. Layout placeholders, lifecycle documentation and Storage onboarding follow separately. The orchestrator will run council review after the round. The fixture does not yet prove native browser loading or visual/layout performance; that bounded proof is a later, separately scoped step.