I don't think so. One example: on Windows, vscode changed the behavior of scroll bars -- something that has been a standard since the mid-80s. They changed the paging behavior and removed the end buttons. Unbelievable.
End buttons on scroll bars are a remnant from when scrolling was new. macOS has done away with them entirely. It's been decades since I interacted with one, so no, I don't miss them at all.
So, I'm not denying that the situation on Windows is inconsistent when you factor in UIs that Microsoft is trying desperately to update, but the design language around scrolling in modern UIs just doesn't seem to be a real problem (outside of accessibility, obviously, which needs special attention regardless).
> design language around scrolling in modern UIs just doesn't seem to be a real problem (outside of accessibility, obviously, which needs special attention regardless)
This is another difference between the mentality today vs. the mentality back then. Accessibility should not need "special" attention. It should be baked into the product. Enough users lack the ability to comfortably drag while clicking, that you don't want to first release a product that doesn't work for them, and then later fix it as a bug. You need to consider Accessibility from day one, during the early design. Just like you need to consider security vulnerabilities and user privacy from day one. They're not things that get tacked on at the end.
But this example isn't even about considering Accessibility holistically. The devs just flat out -removed- the scroll end caps from the product! This wasn't an oversight or some UX over-eager designer accidentally going overboard. They deliberately went out of their way to remove a standard control.
I don't know about Windows 11, but on Windows 10 end buttons remain standard. Do you also think that diverging from consistency with the host platform is acceptable?
