Conversation
…60930 perf(web): preserve home map across viewport changes
chore(release): promote home map continuity to data
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
1 participant
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.
Promote the verified home-map continuity change from data into main through the protected release path. Breakpoint changes retain the map and restaurant selection, share one viewport snapshot for detail/control chrome, desktop-scope collapse state, and clear mobile fullscreen/sheet CSS on desktop entry.
PR #3067 retains the full-tree production-bundle measurements and independent validators: 31 alternating local pairs show readiness 27.5→18.7 ms (−8.8 ms, −32.0%; noise 4.8 ms), map recreation 1→0, and markerless DOM frames 1→0. Frame callback gap is unchanged. Chromium and WebKit real-provider baseline observations are retained separately. The structural result is 0.445→0.075 ms (−0.370 ms, −83.1%; noise 0.060 ms).
Relevant unit, browser, lint, type-parity and protected checks must pass. No hosted speedup or complete flicker claim follows from local fixtures. Production delivery requires exact deployment SHA and live domain/provider readback; named rollback SHA: 157ced9.