You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs-dev@perl.apache.org by Stas Bekman <st...@stason.org> on 2002/01/03 06:26:34 UTC
on menu/body location problem
I've noticed that the HTML for the menu comes after the main content
body. So if CSS is not supported you get the menu at the bottom, since
it's the last one in the HTML sequence.
Wouldn't this problem go away if we put the menu HTML code first? Any
reason for putting it last?
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:stas@stason.org http://ticketmaster.com http://apacheweek.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: on menu/body location problem
Posted by Thomas Klausner <do...@zsi.at>.
Hi!
On Fri, Jan 04, 2002 at 12:27:39PM +0100, lambretta@inet.uni2.dk wrote:
> +1 for putting the 'left content' divs (menu, ads etc) in the upper part of the
> html code
OK, I'll change that.
--
D_OMM +----> http://domm.zsi.at <-----+
O_xyderkes | neu: Arbeitsplatz |
M_echanen | http://domm.zsi.at/d/d162.html |
M_asteuei +--------------------------------+
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: on menu/body location problem
Posted by la...@inet.uni2.dk.
> I understand your reasoning. But I doubt it will apply to the majority
> of users. Especially for pages with a very long content. Not very user
> friendly I must say. Users spend most of their time on the page reading
>
> the content, the scrolling down takes a few moments. However when you
> navigate the site looking for what you need to read this is going to be
>
> a huge pain.
>
> -1 on this concept. Shows that I didn't test it with lynx in first place
+1 for putting the 'left content' divs (menu, ads etc) in the upper part of the
html code
./allan (schipol, amsterdam)
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: on menu/body location problem
Posted by Stas Bekman <st...@stason.org>.
Thomas Klausner wrote:
> Hi!
> On Thu, 3 Jan 2002, Stas Bekman wrote:
>
>
>>I've noticed that the HTML for the menu comes after the main content
>>body. So if CSS is not supported you get the menu at the bottom, since
>>it's the last one in the HTML sequence.
>>
>>Wouldn't this problem go away if we put the menu HTML code first? Any
>>reason for putting it last?
>>
> The reason I did it this way is that I personally hate to have to
> scroll down to get to "real" content if I browse a site with lynx.
>
> Currently, if you don't have CSS enabled, the site looks like a "non-frame
> version" but you can still use it very well (although the navigation is
> more gopher-like, but thanks to the prev/next widget you /can/ move
> "sideways").
>
> If the menubar would come first, you'd have to scroll past it on every
> page, which I find annoying.
>
> IMO the page degrades better this way.
>
> Another (minor) advantage is that the content is displayed first. Nobody
> vists the mod_perl site to view our marvelous NavBar, the users are there
> for the content.
I understand your reasoning. But I doubt it will apply to the majority
of users. Especially for pages with a very long content. Not very user
friendly I must say. Users spend most of their time on the page reading
the content, the scrolling down takes a few moments. However when you
navigate the site looking for what you need to read this is going to be
a huge pain.
-1 on this concept. Shows that I didn't test it with lynx in first place
:( and was happy with what I saw under mozilla. Sorry for not doing this
in first place.
Any chance that we can have some very minimal tables to get things
working for non-CSS browsers, without hurting the current design?
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:stas@stason.org http://ticketmaster.com http://apacheweek.com
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: on menu/body location problem
Posted by Thomas Klausner <do...@zsi.at>.
Hi!
On Thu, 3 Jan 2002, Stas Bekman wrote:
> I've noticed that the HTML for the menu comes after the main content
> body. So if CSS is not supported you get the menu at the bottom, since
> it's the last one in the HTML sequence.
>
> Wouldn't this problem go away if we put the menu HTML code first? Any
> reason for putting it last?
The reason I did it this way is that I personally hate to have to
scroll down to get to "real" content if I browse a site with lynx.
Currently, if you don't have CSS enabled, the site looks like a "non-frame
version" but you can still use it very well (although the navigation is
more gopher-like, but thanks to the prev/next widget you /can/ move
"sideways").
If the menubar would come first, you'd have to scroll past it on every
page, which I find annoying.
IMO the page degrades better this way.
Another (minor) advantage is that the content is displayed first. Nobody
vists the mod_perl site to view our marvelous NavBar, the users are there
for the content.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org