Unfortunately, that approach doesn't quite work in all cases either: if you use a fixed width that's wide enough for most sites to render properly (those days, that'd probably have to be 1280px), many sites that try to render in a centered column designed for 800px screens end up having a lot of blank space on the left of the virtual screen, so that in the initial position of the viewport the interesting part of the site is partially or entirely off-screen.
JBQ On Thu, Nov 27, 2008 at 5:56 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I'd like to suggest a change to the Android Browser that may seem > minor but would actually make it much more enjoyable to use. > > Websites with a fixed-width design are flawless on the browser. > Websites that dynamically scale based on window size are significantly > more problematic. A perfect example is the Android Discuss website. > The table to select a which mailing list you want to view appears > squished, with thin columns and ridiculously tall rows. When you zoom > out, though, and wait a moment, they display at a reasonable width. > But you can't read the text because you're zoomed out. > > Solution: take out the portion of zooming which resizes the "window" > of the browser. Render the page at a fixed width that looks good on > most sites, like 1024 or 1280, and just zoom in and out of that. > > This would fix issues with sites displaying differently in landscape > mode as opposed to portrait. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
