FOAK basic html problem

In 1997 browsers didn't fully support them. It was appropriate to avoid
their use.

Its now 2004 and it can be safely assumed that browsers support them.
Disability access problems can be dealt with. It is no longer necessary
avoid their use.

Unless you want to give the impression that you know your internet onions
and show you're an 'old boy' at the game by trotting out the "frames are
bad" line.

 

porl mate, don't use frames - they bite 1997-stylee.

 

Are you being cheeky?

 

you can't touch my bum, no matter how politely you ask.

Seriously though, don't use frames - they make you look like a
no-nothing wanker.

Use CSS for positioning - it's the way forward.

e.g. http://glish.com/css/7.asp

 

First you need to give your button/rollover elements a name with
id="name1"
Each ID has to be unique for that page/frame element but can be reused on
other pages. Some browsers use NAME instead of ID but it doesn't hurt to
have both
eg: id="name1" name="name1"

Then use the onMouseOver="name1.src='highlight.gif'" and
onMouseOUt="name1.src='normal.gif'"

The below code snippet is from an earlier version of my menu page. It was
bad for many reasons but mostly because I had 3 images per button. The
later version has one background image common to all buttons and changes
the style of the overlaid text instead of the image.

<td>
<a href="HomePage.asp">
<img src="Images/Buttons/ButtonHomepage.gif"
id="homepage" border="0" alt="Homepage"
onmouseover="homepage.src='Images/Buttons/ButtonHomepageBright.gif'"
onmouseout="homepage.src='Images/Buttons/ButtonHomepage.gif'"
onmousedown="homepage.src='Images/Buttons/ButtonHomepageClick.gif'"
width="100" height="29">
</a>
</td>

You could use <div> elements instead of <td> elements.

 

I forgot how tedious web sites were to put together.

 

Curiously, they're absolutely fascinating to read about.

 

Heh, that's funny.

 

keeps the spackers and windowlickers happy too.

 

that wasn't the reason to avoid using them.

the reason to avoid using frames is not /accessibility/ per se - it's
/usability/. Frames **** navigation.

heh

 

Look, you know, I know that I know SFA about this stuff. Just let carry
on with my delusions.

 

I've lost interest in that now, but I'm vaguely interested in why your
quote of what I said doesn't include the slashes I put in for emphasis
- did XanaNews strip them, or did you manually edit them out, and if
so, why?

 

Xananews converts the 'tagged' text into actual italics. When I selected
it to reply it had lost the // so was presented as plain text.

Does the same with * and _, unfortunately.

 

ah - that's a nice feature - I got into the habit of slashes for
italics, asterisks for bold and underscores for underline years and
years ago, as most of the popular Fidonet newsreaders did this.

ah - that's not so good.

hmm.

 

here you go, then:

http://www.useit.com/alertbox/ s0w9p0

 

Gee, thanks.