The way full screen worked was clearly intentional, not a bug, they obviously invested a lot of time into making this objectively less useful. Don't talk to me as if I'm an idiot simply because I won't speculate as to why they did this. I only know they did - and that's not some new thing I just made up, it's common knowledge. Don't be so hostile.
> Don't talk to me as if I'm an idiot simply because I won't speculate as to why they did this. I only know they did - and that's not some new thing I just made up, it's common knowledge. Don't be so hostile.
Let's assume best faith. siglesias might have just mean "that design choice makes no sense", not "you make no sense".
On to speculation - I'd guess they don't want you to use full screen, and only included it as a concession to things like movies / games.
> On to speculation - I'd guess they don't want you to use full screen, and only included it as a concession to things like movies / games.
On the contrary, the Lion fullscreen mode, which caused the issue, was a relatively large push towards fullscreen, by giving it a standardized and better (if you don't have multiple displays :) UI and integrating it into built-in applications.
Sorry, you're right, I might have misunderstood him there. As to the speculation, my guess is you're correct there also: they do want to enable people with multiple displays, they just can't imagine why you would want fullscreen like that as well so they make sure you can't. It's probably about dictating "the user experience".
