CSS has the technical capability to handle this situation, but the end
user is stuck with the bill for user's not on unlimited data plans.
Until data packets are cheaper, I feel that it would be better to not
send an entire pc-based navigation. Maybe we need to create a custom
simplified navigation on the server-side.
Also, the data size of the PC page would need to be checked.
chriskk
> The placement of that nav-link div in the rendered output can be
> controlled using CSS. In the HTML file that is the source for that
> rendered output, the nav-link div does not need to physically
> precede the div containing the main content for the page. In the
> HTML file, it can be placed physically after the main body, and
> then the rendered placement of it can be manipulated using CSS.
>
> So if content authors want to design keitai-friendly sites, one
> simple thing they can do to help get there is to start by placing
> navigation and other extra stuff at the end of the source file,
> after the main body, so that users viewing the site without a
> browser that support CSS absolute positioning or floats will get
> the main content at the top of the browser frame, and can then
> scroll down to the bottom of the frame to get to that stuff if
> they need to.
--
b: http://ver2.oreno.org/
e: chriskk@gmail.com
Received on Wed Dec 7 10:34:46 2005