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
I am using user flows to navigate to a url. Then I am opening a timespan and performing a simple scroll to the bottom of the page. However, after testing this on several websites, I am often getting a value of 0 for my CLS from the timespan even when I get a nonzero value from navigate. I know that navigate can only analyze content available on page load, so the layout shift element must be available at page load, but I do not understand why timespan is not also getting this value. I am starting the timespan before performing any scrolling or other interaction. Furthermore, I am using the PerformanceObserver API and observing several layout shift events during the scroll. Can anyone explain this behavior?
The text was updated successfully, but these errors were encountered:
User input close to the shift is ignored in CLS metric. Scrolling doesn't count, but other inputs do (see link). Are you only scrolling or doing more on the page?
I am also performing a click on a selector before the scroll input. However, I have tested it without the click action and am still getting a CLS of 0.
I am using user flows to navigate to a url. Then I am opening a timespan and performing a simple scroll to the bottom of the page. However, after testing this on several websites, I am often getting a value of 0 for my CLS from the timespan even when I get a nonzero value from navigate. I know that navigate can only analyze content available on page load, so the layout shift element must be available at page load, but I do not understand why timespan is not also getting this value. I am starting the timespan before performing any scrolling or other interaction. Furthermore, I am using the PerformanceObserver API and observing several layout shift events during the scroll. Can anyone explain this behavior?
The text was updated successfully, but these errors were encountered: