oh brother… this prob is more complex than I thought…
it turns out it’s for content generated from the back-end (JSP env); I have classic file-includes situation (header & main body, etc…)
so when I do “view src code” copy the code into a page and load it like that, as strictly html with all the markup hard-coded, it works, with both tags, the one I posted and the one you posted, but in JSP is where it gets messed-up… man, that’s just grand… was not expecting to run into this problem with mobile…
(still don’t know if prob is the file-includes or the JSP per se… yikes…)
in the JSP, the content inside the divs occupies the entire viewport, but the width of the wrapper divs is only half the viewport (100% width for the wrapper divs, this is correct, for mobile, right?)
I find it interesting that there is not a single comprehensive guide to mobile application and website usability. With the explosion of smartphones and tablets in recent years and the massive usability industry why is there no such resource? Is is because it’s too big a topic or is it just underserved? I’m not trying to derail this conversation I’m just echoing the poster’s difficulty in finding authoritative information.
[font=verdana]There have been plenty of general usability studies on mobile usage, but in terms of details and specifics, a big problem is that the marketplace is so diverse and fast-moving, and audiences so varied in their capabilities, competencies and browsing habits that it is difficult to pin anything down. If you’re looking at website usability on a PC, you have half a dozen browser/OS combinations that you need to test in, you can check for keyboard accessibility, variable screen sizes and so on … and then you can concentrate on the actual usability. Parameters from the device itself don’t change a lot. Whereas for mobiles there are new phones coming out all the time, and this adds a huge variation into the mix. Different phones work in different ways, different screen sizes have different needs, different people have different needs. What was crucial one year may be largely irrelevant the next.
I’m not saying that mobile development and usability isn’t worth further study – it undoubtedly is, it is where the bulk of future growth lies, but it isn’t a mature technology, and it’s so rapidly evolving that any detailed study would be out of date before it was published.[/font]