Back to journal

The first page should survive the application starting

On October 1, I corrected a page-startup problem on Petricani22.eu. The website could already return useful page content before its interactive code finished loading. On a cold route, however, restoring saved cart or currency state could update the application before it had finished attaching to that initial content. Having content in the first response was only part of the job; the handoff also needed to preserve it.

The correction moved the matching loading boundary in the server and browser renderers above the components responsible for those state updates. This gave the page a consistent boundary while the route code became available. The change was not a new rendering architecture or a redesign. It addressed the order in which the existing application became interactive, so restoring a saved choice would not disrupt the original page during that transition.

The regression check looked for more than a page eventually containing the right text. It verified that the original page elements survived while saved cart and currency state were restored. That distinction matters because a screen can appear correct after startup even if the original document was discarded and rebuilt along the way. Looking at the handoff itself made the check specific to the reported failure rather than relying on the final appearance alone.

The implementation was merged on October 1. The review record includes passing application checks and production-mode local browser inspections of representative bilingual routes, without captured hydration errors in those samples. Category reads and missing bilingual descriptions also received focused corrections in the same patch. Those local results establish tested startup behavior, not a dated production deployment. They also do not prove that every route or every possible saved state behaves identically.

Reflection

Initial content and interaction are two stages of one visit. On Petricani22.eu, the useful correction protected the transition between them. A page that starts with readable information should keep that information stable while the application restores the person's choices and becomes ready for the next action.