I am interested in some of the very strong opinions on the list about the
serving of XHTML compliant documents as text/html. I hope you don't mind me
asking for your opinions and reasons.
I am part of the Arts IT teaching staff at Bathurst TAFE where we teach web
design amongst other
You could use a bit of JavaScript to detect on page load whether the URL
has a hash (#) and then force the jump to there (something like
http://www.brandspankingnew.net/specials/anchorjump/anchorjump_01.html).
That might sort the Safari won't jump to anchors on page load problem.
However it sounds
Steve Olive wrote: [snip]
Are we wrong?
If so, why is this so wrong?
Should we go back to teaching HTML 4.01?
Hi Steve,
When I first started on standards (ca 18 months ago), I read a lot of
things which told me I should be converting to XHTML. so I did. But,
like most 'new' people, I served
Hi,
The padding and margins are consistent:
div#navigation{float:left;width:150px; line-height: 2em; margin-
left:-700px }
div#navigation li a {font-weight: bold; height: 32px; voice-family:
\}\; voice-family: inherit; height: 24px; text-decoration: none}
div#navigation ul
i'm not sure if it is the same thing, but i thought i would mention
it: when i bring it up in 6.0.2, the text doesn't act weird until
i click any of the menu links. after a menu link is clicked, that
item will jitter onmouseover (the height seems to be affected).
a small thing, but i thought it
