wearos.google.com - see bug description

[webcompat-bot]

URL: https://wearos.google.com/

Browser / Version: Firefox 64.0 Operating System: Linux Tested Another Browser: Yes

Problem type: Something else Description: Scrolling down page is way slower than in Chrome Steps to Reproduce: I loaded the page based on a comment on reddit: https://www.reddit.com/r/firefox/comments/9ix5h3/unreasonably_high_energy_use_on_mac/e6nvvxw/ -- I scrolled down the page, and on my machine the page stutters while scrolling. Additionally, the distance I have to swipe on my touchpad to scroll down is significantly more than in Chrome.

Browser Configuration

• mixed active content blocked: false
• buildID: 20180924220148
• tracking content blocked: false
• gfx.webrender.blob-images: true
• gfx.webrender.all: true
• mixed passive content blocked: false
• layers.acceleration.force-enabled: true
• gfx.webrender.enabled: false
• image.mem.shared: true
• channel: default

From webcompat.com with ❤️

[adamopenweb]

In Firefox 64 for MacOS (webrender enabled) on a new MBP it is a bit slower than Chrome. But I wouldn't have noticed without comparing to Chrome. In Safari the entire window shakes up and down, looks pretty bad.

@wisniewskit @denschub Can either of you check this out in Linux and give your thoughts?

[wisniewskit]

I'd wager this is just an instance of bz1210726. I have an nVidia card using the nouveau Linux drivers, and with WebRender (gfx.webrender.all) or just regular hardware acceleration on (layers.acceleration.force-enabled), I can't really feel a difference between Firefox and Chrome (which has hardware acceleration on by default). But with the Firefox default of no hardware acceleration on at all, I do notice more CPU usage and the vertical watch animation in the center of the page is noticeably less smooth.

Users with a relatively common device and driver should be able to manually enable one of the about:config flags I mentioned above to see if it improves performance, though it may cause more issues than it resolves (and of course WebRender won't work at all right now except on nightly builds). Other devices and drivers than mine could have drastically different quality and performance between browsers, especially on Linux.

[softvision-sergiulogigan]

I'd wager this is just an instance of bz1210726.

@denschub can you confirm this?

[softvision-sergiulogigan]

Let's just close this as a duplicate of the mentioned issue.

If anyone can provide more information, please feel free to reopen or comment on the issue.