Posted by dorayme on 12/28/07 19:51

In article <XS3dj.28533$CN4.3725@news-server.bigpond.net.au>,
"rf" <rf@invalid.com> wrote:

> "groovyd" <google@groovydomain.com> wrote in message
> news:3f052019-c1b4-4e2e-8861-c85dc2a54a96@c4g2000hsg.googlegroups.com...
> > everyone keeps telling me that frames are dead and so i feel the need
> > to finally rewrite my 'dead' site (www.groovydomain.com) so that it
> > doesn't use them by somehow crafting some slick CSS that the same
> > everyones are telling me is the new 'fashionable' way.
>
> > Words of wisdom anyone?
>
> Don't try to "emulate" the existing frame site, you will create more
> usability and accessibility problems than you need. Specifically, do not be
> tempted to use overflow: scroll on anything. Redesign the site from scratch.
>

Yes, grab the opportunity to do something different.

But it is not all that hard to emulate frames and avoid creating
more usability and accessibility problems than you need. OP's
site is simple enough. Float the menu left. Repeat it and the
header on each page and like that. There are not that many pages.
He can use includes or not, it does not matter here.


-----------------
(btw, what caught my eye in your remarks, rf, was you saying,
above,

"do not be tempted to use overflow: scroll on anything"

because, your words in another thread were still ringing in my
ears:

"I usually however use overflow: scroll"

I looked into these remarks of yours yesterday in another
connection and I think I learnt something. I was tinkering with
and advancing my little story telling project at
http://netweaver.com.au/floatHouse/ Sure, it was in another
context and I am not saying you are contradicting yourself, keep
your shirt on. What you and especially Ben said about overflow
was most interesting to me.)

--
dorayme

[Back to original message]