fix: stabilize tide hydration across Cloudflare and browsers - #61
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
wxcn | 499a2e2 | Sep 08 2026, 01:51 AM |
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.
Production rendered tide-time separators with a narrow nonbreaking space while Chrome rendered a normal space. React reported a hydration error for each of the four tide cards. Normalize these ICU-dependent separators in the React and Vue components and regenerate their registry items. Also retain the initial React props snapshot through hydration before applying live updates.
Validation: an independent Astra browser probe isolated the four differing text nodes and removed all four errors by normalizing them. The new SSR regression simulates normal, narrow, and nonbreaking spaces; all 11 React tests pass. The production-build browser regression passes both React routes across Chicago, UTC, and Tokyo, including post-mount style updates. Workspace checks, formatting, and the production build pass.
Follow-up to #36. Signed commits only; auto-merge requested after CI.