>
> Matt Fielding wrote:
> >>> http://mattu.isa-geek.com/index2.php
>
> >>> 2)
>
> > Georg, your suggestion about using a margin to displace the content div,
> I
> > thought, would cause the content div to start below the navbar.
>
> First: by not setting a width on navbar you may lose some old
> b
Matt Fielding wrote:
>>> http://mattu.isa-geek.com/index2.php
>>> 2)
> Georg, your suggestion about using a margin to displace the content div, I
> thought, would cause the content div to start below the navbar.
First: by not setting a width on navbar you may lose some old
browser-versions - t
>
> Matt Fielding wrote:
> > http://mattu.isa-geek.com/index2.php
>
> > 1)
>
> You can solve the resizing problem by adding a padding to those links -
> same size and the borders, and remove it on :hover.
>
> > 2)
>
> The simplest solution is to not float it. Instead, keep it in normal
> flow and a
Matt Fielding wrote:
> http://mattu.isa-geek.com/index2.php
> 1)
You can solve the resizing problem by adding a padding to those links -
same size and the borders, and remove it on :hover.
> 2)
The simplest solution is to not float it. Instead, keep it in normal
flow and adjust with margins
First off, if you visit http://mattu.isa-geek.com/index2.php you will see a
layout I am currently testing and coding. So far I have two problems I'd
like to get some input on.
1) using :hover on anchor elements with display:block styles, being the most
compatible method, causes a few problems with
