Earlier quoted context omitted.
Why would anybody want to enable zoom in the first place? Properly designed mobile web apps should already have decent sized text and graphics. In addition to the iOS orientation bug you mention, there's also that annoying click delay. A lot of people at StackExchange seem to recommend zooming though: http://ux.stackexchange.com/questions/19464/should-mobile-op...
Because on a small screen the size vs data density tradeoff has a sweet spot that varies from one pair of eyeballs to the next.
The Scroll Up Bar
101–110 of 118 posts
Re: The Scroll Up Bar
#102I suspect this was influenced by the browser behavior in iOS 7. Almost all the browser chrome (full address bar and status bar) disappears when you start scrolling but reappears if you scroll back up quickly. In fact, the iOS behavior is rather more nuanced: * Scrolling down hides chrome * Swiping up quickly reveals chrome * Scrolling up slowly does not reveal chrome * Scrolling to the top of the page reveals chrome…
Re: The Scroll Up Bar
#103"Creeper" nav bars (an appropriate term, I think) are partly a consequence of mobile devices not letting you instantly jump to the top of a page. Mobile devices should offer a snappy, intuitive way to jump to the top or bottom of a page.
Re: The Scroll Up Bar
#104Re: The Scroll Up Bar
#105Earlier quoted context omitted.
Because on a small screen the size vs data density tradeoff has a sweet spot that varies from one pair of eyeballs to the next.
Yeah, that's true. But are we talking eyeballs within the same age group, or like teens vs. old people?
Re: The Scroll Up Bar
#106Earlier quoted context omitted.
There was/is an iOS bug where changing orientation after zooming would cut-off some of the page, most websites simply disable all zooming to "fix" it. http://blog.pgrady.com/post/29511322784/fixing-the-ios-orien...
Why would anybody want to enable zoom in the first place? Properly designed mobile web apps should already have decent sized text and graphics. In addition to the iOS orientation bug you mention, there's also that annoying click delay. A lot of people at StackExchange seem to recommend zooming though: http://ux.stackexchange.com/questions/19464/should-mobile-op...
Re: The Scroll Up Bar
#107Earlier quoted context omitted.
There was/is an iOS bug where changing orientation after zooming would cut-off some of the page, most websites simply disable all zooming to "fix" it. http://blog.pgrady.com/post/29511322784/fixing-the-ios-orien...
Why would anybody want to enable zoom in the first place? Properly designed mobile web apps should already have decent sized text and graphics. In addition to the iOS orientation bug you mention, there's also that annoying click delay. A lot of people at StackExchange seem to recommend zooming though: http://ux.stackexchange.com/questions/19464/should-mobile-op...
Re: The Scroll Up Bar
#108Earlier quoted context omitted.
Why would anybody want to enable zoom in the first place? Properly designed mobile web apps should already have decent sized text and graphics. In addition to the iOS orientation bug you mention, there's also that annoying click delay. A lot of people at StackExchange seem to recommend zooming though: http://ux.stackexchange.com/questions/19464/should-mobile-op...
I may want to zoom to see an image up close, or just to change text size. Outside apple, phone screens vary widely, and so do text sizes. You can't hope to find one that works on all phones for everyone.
Re: The Scroll Up Bar
#109Am I the only one who prefers to read websites in "desktop" mode? I always feel totally alienated by the mobile page, there is information left out, annoying badly-implemented JS scrollers, etc... The "desktop" site looks always more nice and familiar, and you can zoom and scroll around as you wish to read everything.
Just the damned copy.
If you've got navigation elements, don't cram them into sidebars. Put them at the top of the page (but not fixed), or bottom (dittos).
For a huge number of sites, I disable presentation of headers, footers, and sidebars entirely. I'm not on the sites frequently enough to care to use them.
Some mobile sites do pretty well by removing extraneous elements, others cram in more fixed elements (top, bottom, or side), all of which send me running. There's simply not sufficient real estate to deal with that crap.
Increasingly, Web design isn't the solution, Web design is the problem.
I've suggested gently to the author of this site that he'd do better with balanced left/right margins, a 45em or so content width, semantic markup, and white backgrounds, but he's apparently not interested:
http://www.billdietrich.me/Reason/ReasonConsumption.html
Seriously, when the easiest way to read content is to grab plain text via lynx or w3m, add Markdown, and re-export the page as HTML or PDF, you're doing it wrong.
Re: The Scroll Up Bar
#110I don't get why these bars are being used everywhere, personally I find them annoying. Scrolling up takes like half a second...
The sole reason is branding. Websites don't want you just reading content; they want you reading content on their site . The most obvious way to remind you that you're reading it on their site, and thus convince you to come back, is a fixed header bar.
I realize I'm likely a very small portion of the demographic, by my prior two decades' experience with Web Annoyances tells me that my own sentiments aren't much different from those of the typical Web user, it's just that I'm aware of, and make use of, tools to fix many of the problems.