RE: Cross browser issue with position:absolute...
by Emily Berk <emily(at)armadillosoft.com>
||Thu, 06 Jan 2005 05:29:13 -0800
"'Emily Berk'" <emily(at)armadillosoft.com>,
Thanks again for your interesting comments.
except for this one browser (IE for Mac). I think.
So, I think if I trade off ALL IE for Windows with NO IE for Mac, I've probably still made the right choice.
Too bad I have to make this choice, but from what I can tell, I do have to make a choice.
Do you agree that this is the choice that I am making?
At 10:29 AM 1/6/2005 +0200, Sophia Kapterian (E-mail) wrote:
>To eliminate rendering inconsistencies you must avoid proprietary or
>deprecated tags and have valid markup. Browsers use some form of error
>correction to guess what the page should look like when they encounter
>invalid html and no two browsers will guess the same. So if you want to
>create forward-compatible sites, take the time to correct the markup.
>You actually don't have that many errors. The validator will refer to about
>26 in your markup but there are actually two main ones:
>the <DEFANGED_layer> element which is Netscape proprietary tag and the <ul> for the navigation. ...
>... The other error refers to the - behavior:url("hover.htc") in #navcontainer li - which is not terminated with a semicolon. This is to make ie understand :hover on elements other than <a> but fails css validation.
>There are a number of resources for dropdown menus with pure css and
>For a popular dropdown, read the article at alistapart for Suckerfish
>The final example is posted here:
>You can also check out the multimenu at csscreator with a number of other
>helpful resources: http://www.csscreator.com/menu/multimenu.php.
HWG hwg-style mailing list archives,
maintained by Webmasters @ IWA