Is floated right navigation considered bad or OK?

Hi xyZed,

There is circumstantial evidence that on Wed, 15 Feb 2006 09:28:29
+0100, TomekK <tomekk.nospam.delete__it (AT) amsnet (DOT) pl> wrote

› The key to success is the Box Model. If you would use DIVs instead of
› TABLEs to divide your layout parts you could do almost everything with
› them applying accurate CSS positioning.

I suspect the answer is very simple but it eludes me :-) I don't have
a single table on my site. I have the content DIV floated left and the
Nav column DIV floated right. But if I place the Nav column "before"
the content DIV, then the content doesn't display until the bottom of
the Nav DIV.

Use float right for both DIVs representing columns and see what you
would get ;-)

Of course you would need one extra div as a container for columns
otrherwise they would stick to the right window frame.

Tomek

Hi,

I suspect the answer is very simple but it eludes me :-) I don't have
a single table on my site. I have the content DIV floated left and the
Nav column DIV floated right. But if I place the Nav column "before"
the content DIV, then the content doesn't display until the bottom of
the Nav DIV.

One more solution: if you are 100% sure that your content column would
be longer than menu column at every single site you could use absolute
positioning for menu DIV.


Tomek

xyZed <xyzed (AT) xyzed (DOT) co.uk> wrote:

Is there any evidence that right navigation affects SERPs due to it
being placed after the content in the markup?

No, since that would be extremely silly.

Also are there any
usability issues with it, and ways round them?

The scroll bar is to the right, "we" read left->right, so that's why the
menu is to the right. IIRC this has been researched :-) Note that
something can be somewhere not because it's the best design, but because
people are used to find it there.

--
John isa Perl programmer: http://johnbokma.com/perl/perlprogrammer.html

Fox G Bar: http://johnbokma.com/firefox/google-...stomizing.html