From add7d82b105c0af2ded2a97906de10d17078d060 Mon Sep 17 00:00:00 2001 From: Rich Harris Date: Thu, 31 Aug 2023 11:35:56 -0400 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Geoff Rich <4992896+geoffrich@users.noreply.github.com> --- documentation/blog/2023-08-31-view-transitions.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/documentation/blog/2023-08-31-view-transitions.md b/documentation/blog/2023-08-31-view-transitions.md index 35f7634fee..11d0dc6e5e 100644 --- a/documentation/blog/2023-08-31-view-transitions.md +++ b/documentation/blog/2023-08-31-view-transitions.md @@ -74,7 +74,7 @@ onNavigate((navigation) => { With that, every navigation that occurs will trigger a view transition. You can already see this in action – by default, the browser will crossfade between the old and new pages. - +
How the code works @@ -158,7 +158,7 @@ header { Now, the header will not transition in and out on navigation, but the rest of the page will. - +
Fixing the types @@ -210,7 +210,7 @@ li[aria-current='page']::before { By adding that single line, the indicator will now smoothly slide to its new position instead of jumping. - + (It might be easy to miss the difference – look at the small moving triangle indicator at the top of the screen!)