Modern client-side routing: the Navigation API | Web Platform | Chrome for Developers

Single-page applications, or SPAs, are defined by a core feature: dynamically rewriting their content as the user interacts with the site, instead of the default method of loading entirely new pages from the server. While SPAs have been able to bring you this feature via the History API (or in limited cases, by adjusting the site's #hash part), it's a clunky API developed long-before SPAs were the

[tofu-kun]

History API の代わりになる Navigation API 。まだ Chrome のみの対応だが

[mizchi]

history.pushState の代わりになるやつか

[Pasta-K]

これ絶対に使いたいな

[efcl]

Chrome 95にてフラグ付きで実装されたApp History APIについて。 問題のあるHistory APIを置き換えるAPI。 `navigation`イベントでのナビゲーションの検知、`transitionWhile(promise)`での遷移中/成功/失敗の表現、ナビゲーションエラー時のロ