> Thanks Robert,
>
> My apologies, I wasn't specific enough. My question was intended to point
> towards CSS issues of using flow in the way under consideration. So I should
> have written, "what are the CSS pitfalls, if any?"
>
> I accept, of course, there are other issues, especially accessibility ones,
> but they are outside the scope of CSS and can perhaps be conquered by other
> means including adequate content placement.
>
> Mike A
No worries Mike I've done the same thing myself,
I guess just using appropriate headers in the content would be
enough for the accessibility. CSS-wise i think position: absolute or
fixed could work. If I were you I would give the header a height in ems
and pad the body at the top with the equivalent amount of ems to allow
for re-sizing. I use this method to position the navigation at the top
of the page
usually.
If the navigation and header are images in which case fixed pixel
heights etc... are better suited.
As far as pitfalls go it's down to cross-browser rendering of
absolutely positioned elements. I use the strict-mode doctype nearly all
the time now and have a lot fewer issues with layout as a result. If
you're just positioning an h1 at the top it should be straight-forward.
Hope this helps,
Rob
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
