undefined | Better HN

0 pointsdilap3y ago0 comments

Huh, yeah, turning on "Reduce motion" does indeed disable bounce scroll in Firefox. Definitely a strange choice on their part! (It doesn't affect it in other apps.)

> I changed my system settings, as I don’t like the default speed and acceleration

I see, that could make sense, if Safari was honoring those changes and Firefox wasn't, in some way. I've got mostly stock settings (slightly bumped up speed and three-finger drag) and it feels spot-on.

0 comments

4 comments · 2 top-level

mmis10003y ago· 1 in thread

> Huh, yeah, turning on "Reduce motion" does indeed disable bounce scroll in Firefox. Definitely a strange choice on their part! (It doesn't affect it in other apps.

The current safari bounce effect bounced ALL fixed elements when you bounce the page body. And by copy that. It basically make youtube(or probably any similierly designed website) unusable for anyone have motion sickness. Because the most part of UI is fixed. And hense it is part of "Reduce motion" setting.

Side notes: Safari agreed that bouncing fixed elements is a bug after Firefox implemented it. So this effect will probably be reverted later.

dilapOP3y ago

Interesting. OK, so I think two things here, if I understand you correctly:

– Bounce effect IS disorienting for some people in some contexts. Hence the decision to disable it in line w/ "Reduce motion" pref.

– On YouTube, Safari bounce-scrolls the whole page, whereas Firefox just bounce-scrolls the scrollable part. I agree the Firefox behavior seems better here (and it sounds like Safari might adopt it).

jbverschoor3y ago· 1 in thread

It's not a choice.. It's just people trying re-implement "native" behavior. Doesn't work. Just use native components.

Firefox never felt native. Typography is different from my system settings, window color is different, mouse behavior different, scrolling behavior is different, spacebar to scroll jumps, zoom is weird.. actual size is 125%. So I always have to zoom out a few times to get to 100%, and it doesn't remember those settings.

The only reason I use firefox sometimes is because I can use different profiles as tabs in the same window. For those pesky apps without multi-account / account-member-user schema.

I used to love firefox 15+ years ago.. when I was still on windows, and IE was really bad, but switched to chrome the moment it came out.

dilapOP3y ago

It's gotta be a choice, right?, since they're enabling or disabling the bounce scroll based on the pref. If it was just system-agnostic the pref wouldn't make a difference.

My understanding is all of the browsers contain a lot of custom widgets. Like, Safari is not drawing text using NSTextView or whatever.

Looking at Firefox and Safari side-by-side they look pretttty similar to me. Some very slight text rendering differences, and Firefox is maybe a touch less smooth to scroll than Safari. The bounce-scroll is a little bit more stiff.

I recorded a video if you want to see what I'm seeing:

https://www.youtube.com/watch?v=-lkAy0O5EDs

There are so many different widget implementations out there now, maybe I'm just losing my sense of what "native" is. But the scroll physics feel right to me, the text looks right, the text selection and input and shortcuts all work...native enough for me!

j / k navigate · click thread line to collapse

0 comments

4 comments · 2 top-level

mmis10003y ago· 1 in thread

> Huh, yeah, turning on "Reduce motion" does indeed disable bounce scroll in Firefox. Definitely a strange choice on their part! (It doesn't affect it in other apps.

Side notes: Safari agreed that bouncing fixed elements is a bug after Firefox implemented it. So this effect will probably be reverted later.

dilapOP3y ago

Interesting. OK, so I think two things here, if I understand you correctly:

– Bounce effect IS disorienting for some people in some contexts. Hence the decision to disable it in line w/ "Reduce motion" pref.

jbverschoor3y ago· 1 in thread

It's not a choice.. It's just people trying re-implement "native" behavior. Doesn't work. Just use native components.

The only reason I use firefox sometimes is because I can use different profiles as tabs in the same window. For those pesky apps without multi-account / account-member-user schema.

I used to love firefox 15+ years ago.. when I was still on windows, and IE was really bad, but switched to chrome the moment it came out.

dilapOP3y ago

It's gotta be a choice, right?, since they're enabling or disabling the bounce scroll based on the pref. If it was just system-agnostic the pref wouldn't make a difference.

My understanding is all of the browsers contain a lot of custom widgets. Like, Safari is not drawing text using NSTextView or whatever.

I recorded a video if you want to see what I'm seeing:

https://www.youtube.com/watch?v=-lkAy0O5EDs

j / k navigate · click thread line to collapse