> they only started hiding them because it looked 'cleaner' to some UI designer.
They started doing it on mobile in order to give more screen real estate to the content area. This was then translated to desktop apps at the same time desktop screen real estate became a non-issue for everyone (a 32" monitor at 1600x1200 used to be a luxury, now it's mundane). Now no one knows if there is anything "below the fold" without initiating a scroll action, which just encourages people to further only focus on the above the fold content.
Interestingly the response to that was sites adding horizontal "progress bars" across the top of the viewport to indicate how much you had read. And with application and website control of the styling and operation of these standard widgets, everyone is slightly different, which increases time to become familiar.
It's been a race to the bottom, in the name of (the subjective at best) "clean design".
They started doing it on mobile in order to give more screen real estate to the content area. This was then translated to desktop apps at the same time desktop screen real estate became a non-issue for everyone (a 32" monitor at 1600x1200 used to be a luxury, now it's mundane). Now no one knows if there is anything "below the fold" without initiating a scroll action, which just encourages people to further only focus on the above the fold content.
Interestingly the response to that was sites adding horizontal "progress bars" across the top of the viewport to indicate how much you had read. And with application and website control of the styling and operation of these standard widgets, everyone is slightly different, which increases time to become familiar.
It's been a race to the bottom, in the name of (the subjective at best) "clean design".