{"id":351987,"date":"2021-09-15T15:39:08","date_gmt":"2021-09-15T22:39:08","guid":{"rendered":"https:\/\/css-tricks.com\/?p=351987"},"modified":"2021-09-15T15:39:10","modified_gmt":"2021-09-15T22:39:10","slug":"2021-scroll-survey-report","status":"publish","type":"post","link":"https:\/\/css-tricks.com\/2021-scroll-survey-report\/","title":{"rendered":"2021 Scroll Survey Report"},"content":{"rendered":"\n

Here’s a common thought and question: how do browsers prioritize what they work on? We get little glimpses of it sometimes. We’re told to “star issues” in bug trackers to signal interest. We’re told to get involved in GitHub threads for spec issues. We’re told they do read the blog posts. And, sometimes, we get to see the results of surveys. Chrome ran a survey about scrolling on the web back in April and has published the results<\/a> with an accompanying a blog post<\/a>. <\/p>\n\n\n\n\n\n\n\n

“Scrolling” is a big landscape:<\/p>\n\n\n\n

From our research, these difficulties come from the multitude of use cases for scroll. When we talk about scrolling, that might include:<\/p>