[eviks]

> Or if there is another way

Of course there is a much better way for all your troubles! Window move: hold a modifier and click&drag anywhere in the window area instead of wasting time precision hunting the titlebar. Window resize: same, use a big 30%-window-width area close to the border instead of hunting for those few pixels of an actual resizable border Horizontal scroll (though strange, Win 11 explorer has horizontal scrollbar immediately visible, though maybe that's a config?): hold a modifier and use the more convenient mouse wheel (or use a window manager with shortcuts or visual grid) None of that, of course, is part of your unhelpful OS

> But modern design lunacy dictates that this scrollbar must be INVISIBLE.

In a real modern design there is no lunacy as wide/tall scrollbar is mostly a space waste as you have better control options, and narrow/short ones are still that, but also unergonomic to use. So you'd have a wide/tall invisible one, which in those smaller % of cases you need them would become visible, but still wide/tall ones

> I, director Skinner and Homer's dad did not get the memo.

That's unfortunate indeed that the bad old ways of window management and scrolling persist for so long and the better ways aren't integrated in the OS

[lsaferite]

Your suggestions highlight what I hate about the new Android gestures interface. You have to know those patterns in advance and remember them. They aren't visually apparent like scroll bars, drag handles, titles bars, and window frames. I am quite versed in keyboard shortcuts, but keeping *all* of them in my head gets a bit much sometimes. When I forget one, rediscovering it is a serious PITA. The rediscovery (or initial discovery) is orders of magnitude harder for things like the Android gesture interface.

Couple this with App and OS designers feeling a *constant* need to change things and make them "better" and you have a disaster in the works. I've been grousing about Android changing things just to change them as I get older. The other day even my 12 y/o daughter was complaining about them changing how things worked.

Anyway, my point is simply two-fold. First, any UI that requires knowing and remembering interactions that aren't easily discovered *is a problem*. Second, constantly changing UI interaction patterns, even when they are discoverable, *is also a problem*.

[eviks]

Oh, sure, those are indeed major fails in all of the OSes - no guides and no easy way to find anything about fundamental operations (it should be easier than googling).

But these are separate issues. For example, even with the scrollbars there can be a change between two behaviors: click on the empty bar jumps to that % or jumps by 1 page. And one can be a click and another a Shift-Click - where in the OS would you discover that??? And the scrollbar width - can only find a registry hack to restore that from some tech article/blog post/ etc, nothing in that waste of the Win 11 Settings app.

[funcDropShadow]

But with a visible scrollbar you would have a visible indication which behavior you triggered. If the scrollbar is invisible you get a changed viewport in both cases but you have to infer which gesture triggers which behavior.

[eviks]

No, when you use a scrollbar it becomes visible, so you get exactly the same indication