On Fri, Aug 28, 2026 at 8:45 AM Anton Bershanskyi <[email protected]> wrote:
>>> Given the above point, I don't think people are used to that idea >>> anymore. Also things like `localStorage` service workers and other >>> aspects stay alive on navigations. >>> I think that the notion that a navigation is a state reset is useful, >>> but if taken too rigidly, it pushes people towards an SPA architecture >>> that breaks all these assumptions from the start (SPAs can even >>> intercept "hard refresh"). >> >> >> Really? How? Via a service worker or by intercepting a key stroke? Even if >> they can, it seems like doing so might be a bad idea, UX-wise ... Sorry, it can intercept programattic calls to `navigation.reload()` (which is also something I'd like to reconsider tbh. I think reloads should be only a browser UI thing) What I said earlier was inaccurate. Retracting my last parenthetical (though the rest of the argument stands) >> >> I don't actually see the words "first render" in that spec (or anywhere else >> in the HTML standard), but I do see "during the first `update the render` >> step" in a Note, so I'm guessing that's what you're referring to. Maybe the >> text should say "before the pagereveal event first" or "before the first >> `update the render` step that display up-to-date content", or the text >> should explicitly define "first render" as that? Sure, the explainer can probably be more explicit about that. Deferring that to @Joey Arhar. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYaT6UiS%2Bufb0xjjfag-%2BPzr7nsbMj%3DomjhQBKhkKoH_wA%40mail.gmail.com.
