Repository navigation
fix(favicons): let a mounted icon retry once its failure ages out - #9501
Merged
Merged
Conversation
A failed load set per-instance state that pinned the icon to its fallback until it unmounted, so the five-minute miss window never reached an icon already on screen. The module-level miss cache is now the only failure record; a reducer only re-renders on error, so the next render after the entry expires asks again (a confirmed miss is still answered from the HTTP cache).
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
 [Medium impact] This PR appears safe to merge. Summary
Reviews (1) · Last reviewed commit: "fix(favicons): let a mounted icon retry ..." · Reviewed by Greptile |
This branch was previously deployed
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.
Summary
<Favicon>to its fallback until it unmounted or its host changed, so the five-minuteknownMisseswindow (the route's outage retry window) never reached an icon already on screenknownMissesis now the only failure record: render checks it alone, and a reducer just re-renders on error. The next render after an entry expires asks again; a confirmed miss is still answered instantly from the browser's HTTP cache (204,max-age=3600), and an outage (204,no-store) is actually retriedType of Change
Testing
lib/faviconand the message-content suites that render source icons (206 tests)check:client-boundary,check:source-conventions,check:comment-hygiene,check:file-names,check:utils,check:test-patterns,check:source-textChecklist
test-auditauthoring gate)