New issue
Advanced search Search tips

Issue 713982 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug

Blocked on:
issue 526463



Sign in to add a comment

https://motherboard.vice.com/en_us/article/its-like-tweeting-but-you-cant-use-the-letter-e scrolls very slowly

Project Member Reported by esprehn@chromium.org, Apr 21 2017

Issue description

Google Chrome	57.0.2987.140 (Official Build) beta (64-bit)
Revision	0
Platform	9202.61.0 (Official Build) beta-channel reef

This was reported through hacker news:
https://news.ycombinator.com/item?id=14159734

hashhar writes:
"""
[...] use Chrome Canary to browse https://motherboard.vice.com/en_us/article/its-like-tweeting-but-you-cant-use-the-letter-e and then use Firefox Nightly. Chrome can barely manage to keep up with scrolling while Firefox chugs along nicely.
"""

What steps will reproduce the problem?
(1) Start loading the page.
(2) Try scrolling.

What is the expected result?

Scrolls smoothly.

What happens instead?

Very sluggish.
 
Description: Show this description
Blockedon: 526463
Mergedinto: 706175
Owner: sahel@chromium.org
Status: Duplicate (was: Untriaged)
There's an 85ms long scroll event handler on my beefy desktop.

For wheel scrolling, we're hitting the main thread every wheel tick, and they aren't.


I'm duping this on the wheel latching bug.

This works fine with touch in Chrome, and badly with keyboard in both browsers.

I haven't dug into to see whether or not their first wheel event is hitting the main thread. I assume it is, and either way, scroll latching will give us 99% of the benefit.

Sign in to add a comment