111–120 of 172 posts
Earlier quoted context omitted.
Why? The window and its position shouldn't matter to the app. My tiling window manager doesn't care what your snowflake app thinks it wants, and I don't either.
The its only fair that complex applications don't care about how well they work under your snowflake WM either.
Earlier quoted context omitted.
Kiosks by definition don't alow users to modify the ui. they run in kiosk mode
You'd be surprised
There are kiosks used for public browsing, where the user has access to full browser app window and can change elements.
There are also ways to get around kiosk mode restrictions, or at least there were for Windows in kiosk mode back in the day. We used it to get browsing access or to just mess with the kiosk. The fun!
Earlier quoted context omitted.
> The point of centering an element horizontally is to make sure that the content you’re viewing is directly in front of you. That's an awfully big assumption. For starters, you're assuming that the browser window itself is centered on the screen, and that the device is centered in front of the user. I don't think this is the point of centering an element horizontally at all, and the result you have created here is n…
I use Firefox with a vertical tabs extension open all the time. Occasionally (rarely, mind) I run into sites that don't bring their full content into view unless I hide the tabs list. Guess they think like the OP.
I'm confused about why this website is using less than half of my window for content. I understand wanting some margins, but a third of my window on each side seems pretty egregious. At least it's centered though!
wrapping text at 55-75 characters per line is often recommended in digital typography by UX. research implies that an optimum length exists to maximize reading speed, and although it depends on many factors 55-75 is often parroted as a universal rule.
To be fair, I read fairly quickly, so maybe this is true if you only read 100 words per minute or whatever.
The sidebar reduces the size of the viewport, and the viewport is what you're centring within. This is obvious and sensible behaviour from Firefox. Please don't centre based on screen res or whatever. Basing your centre position on anything other than the viewport is user-hostile behaviour.
Earlier quoted context omitted.
Joke’s on you: my browser window isn’t centered.
Ah but see, exploiting a Chromium API has let us know you've got this second screen on the side, so we're centering the div on your overall work space. PS: if you switch from the touchpad to a wireless mouse, we'll move the div accordingly
2. The demo doesn't even work, the div stays centered in the viewport, not the program window when I open a side bar (Firefox).
3. Rarely does my browser even cover the center of my workspace, so it would be impossible to center anything in the center of my view without forcibly moving the program window from within the website.