 |
|
 |
|
On Thu, 05 Nov 2009 11:44:26 GMT, "rf" <...@z.invalid
"Barely Audible" <...@mid.individual.net...
As an alternitive question might I ask why you want to specify a "page
width" anyway.
If you simply fail to specify anything at all to do with page with then the
page will automatically adjust to the with of the browsers viewport, no
matter what technology that browser is running on. That is how browsers
work, before web authors cripple them by over specifying things.
|
|
 |
|
 |
|
|
|
|
On Thu, 05 Nov 2009 11:47:16 GMT, "rf" <...@z.invalid
"rf" <...@news-server.bigpond.net.au...
Strewth. I must have a sore d fingure. s/with/width/g
|
|
|
|
|
|
|
|
|
On Thu, 5 Nov 2009 04:57:47 -0800 (PST), Andy Dingley <...@codesmiths.com
On 5 Nov, 11:26, Barely Audible <...@but.here
Not really. If you want this sort of tailoring, you need to look at
server-side dynamic behaviour based on browser sniffing (a ghastly
notion at best, but barely excusable here). Protocols like CC/PP
promise much, but don't deliver too well. It's actually quite hard to
determine "mobile vs. desktop" and sniffing for the OS is generally
more robust than sniffing for browsers and less often spoofed.
Really though, go read the free online copy of Joe Clark's book on
accessible web design. In particular, read the sections on the
importance of a well-linearised site, and on fluid design.
Fluid design makes your site content render usefully well no matter
what the window width (remember it's window, not screen, that
matters). It can't render "as well" (it's smaller), but it does mean
that things don't break and your sideways positioning gracefully
degrades to a vertical stack as necessary, without either truncation,
overlap, or (ideally) needing to use sideways scrolling as well.
Fluid design is important (and important purely for desktops) but even
that's not enough. Most mobile browsing now (compared to 5 years ago)
is done through palmtop and tablet devices that have a reasonable
screen width of 600 or 800, rather than the pure phone of 200 square.
However they're still short on connection bandwidth. Their browsers
should render incrementally as content appears (Opera is noticeably
poor at this, just look at the Nokia 800 tablets). Sites should also
be very careful about their linearisation order, and in not serving
superfluous content (mostly excess ads) that make page access unusably
slow. These are server-side issues, not client-side!
No matter how clever your page design and how fluid your CSS layout
is, getting good usability to today's tablet devices requires a
careful allocation of bandwidth, and that's why we're back looking at
user-agent sniffing.
|
|
|
|
|
|
|
|
|
On Thu, 05 Nov 2009 10:41:34 -0500, Sherm Pendley <...@shermpendley.com
Barely Audible <...@but.here
That's what will happen automatically, unless you've taken specific steps
to restrict your page to a fixed width. If you *are* using a fixed-width
layout, you're beginning to understand why that's a bad idea. So stop
doing that. :-)
sherm--
|
|
|
|
|
|
|
|
|
On Thu, 05 Nov 2009 20:37:20 +0000, Barely Audible <...@but.here
Thanks David I do believe that answers my question!
--
TTFN
Jim
There is no problem that cannot be solved by the use of large
quantities of high explosives.
|
|
|
|
|
|
|