You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title={'This is only informational, your activity on this website is being tracked for analytics purposes and demonstration on how to perform analytics with Next.js and Amplitude (this uses userSessionContext store provider)'}
115
-
>
116
-
Device id (analytics):<br/>
117
-
<DisplayOnBrowserMount
118
-
// When using SSR, we want to render the deviceId immediately because we have access to it through server cookies
119
-
// When using SSG, we need to wait for the browser render because we don't have access to the cookies when generating the static page
120
-
// To test the different behaviours, refresh the both /examples and /products page with JS disabled
121
-
// and notice how the deviceId is properly included in the HTML with SSR (/products), unlike SSG (/examples) where it's empty
122
-
123
-
// XXX This example showcase this complex behaviour. You may want to do something similar for a "Profile" section in <Nav>,
124
-
// that can be rendered using both SSG/SSR depending on the page, where SSR should render the component but SSG should wait for browser re-render
{t('footer.privacy.link','Politique de confidentialité')}
135
138
</div>
139
+
</I18nLink>
140
+
<div
141
+
css={css`
142
+
margin-top:10px;
143
+
144
+
i {
145
+
cursor: help;
146
+
}
147
+
`}
148
+
>
149
+
<i
150
+
title={'This is only informational, your activity on this website is being tracked for analytics purposes and demonstration on how to perform analytics with Next.js and Amplitude (this uses userSessionContext store provider)'}
151
+
>
152
+
Device id (analytics):<br/>
153
+
<DisplayOnBrowserMount
154
+
// When using SSR, we want to render the deviceId immediately because we have access to it through server cookies
155
+
// When using SSG, we need to wait for the browser render because we don't have access to the cookies when generating the static page
156
+
// To test the different behaviours, refresh the both /examples and /products page with JS disabled
157
+
// and notice how the deviceId is properly included in the HTML with SSR (/products), unlike SSG (/examples) where it's empty
158
+
159
+
// XXX This example showcase this complex behaviour. You may want to do something similar for a "Profile" section in <Nav>,
160
+
// that can be rendered using both SSG/SSR depending on the page, where SSR should render the component but SSG should wait for browser re-render
1 commit comments
github-actions[bot] commentedon Dec 20, 2020
Not what you expected? Are your scores flaky? Run Lighthouse on Foo
If scores continue to be inconsistent consider running all audits on Foo