Just a quickie about validation, you've got an invalid doctype declaration:
!DOCTYPE xhtml PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
the html should be html
just to make it easy here's the proper one:
!DOCTYPE html PUBLIC
A few things I noticed with your html.
Your doctype line has xhtml between DOCTYPE and PUBLIC instead of html.
You are missing xml:lang and lang attributes from your opening html
element.
Here is a suggested correct example of these two lines.
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0
Hello Seona,I haven't looked into the
far-to-the-right sub menu issue yet, but I can fix your validation problem. Your
DOCTYPE is incorrectly written:Current:!DOCTYPE xhtml PUBLIC
"-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"Needs to
Seona,
http://alistapart.com/articles/dropdowns/
This is the best implementation I've seen so far, and I'm using it in a
client site to be launched next week.
Works and extensively tested in:
Win IE 5.0, 5.5, 6.0
Win Moz 1.0.2
Win Firebird 0.7
MacOSX Safari 1.0
MacOSX Mozilla 1.0.2
MacOSX
:[EMAIL PROTECTED]Sent: Friday, 30 January 2004 11:19
AMTo: [EMAIL PROTECTED]Subject: Re: [WSG] Making
my menus work across multiple browsers
Hello Seona,I haven't looked into the
far-to-the-right sub menu issue yet, but I can fix your validation problem.
Your DOCTYPE is incorrectly
I usually do this when I want to feed IE with different values:
selector { rules that work with IE }
parentselector { rules hidden from IE that override the previous rules }
In this case:
selector { left: value; }
parentselector { left: 0; margin-left: value; }
Simon Jessey
I love you forever. *grin* It works just fine now in both. Thank you thank
you thank you. :)
Cheers,
Seona.
-Original Message-
From: Simon Jessey [mailto:[EMAIL PROTECTED]
Sent: Friday, 30 January 2004 12:47 PM
To: [EMAIL PROTECTED]
Subject: Re: [WSG] Making my menus work across
On Friday, January 30, 2004, at 01:11 PM, Hugh Todd wrote:
Justin, you wrote,
The original article couldn't get Safari to work, but somehow I
stumbled upon a solution last night, which I'm yet to figure out, but
I'll report back when I do.
Works for me. Could this be because a) I'm using
