Same. Thank heavens the website doesn't know the position of the browser's window in respect to the screen it's on.
[0]: demo: https://mdn.github.io/dom-examples/screenleft-screentop/
My tiling window manager doesn't care what your snowflake app thinks it wants, and I don't either.
I'm trying to think of any that try to fight the interface quite as much as this.
Yes, some things in some complex applications can break, but there are solutions and, practically, these particular things you listed simply aren't among those that break.
The result is that you can't open open two file property dialogs at once (to compare sizes or dates or any other meta data, it's a common thing one might want to do).
Hopefully you'd agree that Wayland should allow apps to position windows relative to their own windows, at the very least.
It's a design choice.
If you do have that attitude there are a million other OOP style things to throw out for speed and correctness before virtual monitors and coordinating compositors
While the Silicon Valley is merely a figurative Mecca for all things tech, Apple could require people to be facing Cupertino if you want to watch a WWDC stream :D
(And yes, CSS can rotate around all three axes, so you could make a div that resists rotating your device in addition to resisting translation...)
Sometimes there is no size setting that will get the text lines on a page to fit horizontally without making the text too small to read. Making it large enough to read means lots of left and right scrolling which is annoying.
A mode where moving the phone sideways scrolls the text at a matching rate so that the experience is similar to reading a page with a magnifying glass might be handy.
Wrapping is fine on some material, but when there are tables it can be very annoying.