Marc Funaro wrote:
> http://nyslittreedata.advantex.net/new/default/default.htm
> 1. ... Opera seems to ignore my list-style:none on sublist items for
> some reason. It made my CSS a little more complex with regards to
> spelling out the appearance of each level in the navigation, but it's
> something that really makes sense to me. Am I way off here?
Not sure. Haven't had any such problems in Opera lately. Will have to
look into it a bit more. Maybe someone else know what's bugging it.
> 2. Per a suggestion I read that content come before navigation (for
> screen readers or those browsers that won't display CSS), I moved my
> navigation div so that it appears in the HTML below the content area,
> and adjusted my CSS to follow "floating" per one of the alistabove
> articles. Now, I cannot get this layout's content area to look the
> same between FF/Opera and IE, no matter what I do.
It's the 'margin-doubling bug on floats' in IE that needs a "kick in the
butt" :-)
Add this "nonsense" styles...
#leftNav {display: inline;}
#mainContent {display: inline;}
...they are "nonsense" because 'floats' are 'block-elements' and can't
revert to 'inline', but somehow the buggy rendering-engine in IE comes
to it senses when it sees that 'display: inline;' rule on 'floats'.
Other browsers are not disturbed by the "nonsense".
> Is it simply not important enough to worry about having content come
> before navigation in the HTML -- because I had this looking great in
> all three browsers until I moved it around...
It will look fine with the above IE-corrections.
The 'line of thought' that it is better to have main content before a
lot of navigation, makes sense in a non-CSS browser, and most assisting
browsing-software seems to approach web pages similarly - with limited
CSS-support.
It isn't the only 'line of thought' though, as some prefer to pepper
their pages with 'skip to main content' and/or 'skip to navigation',
while others line up everything the old way: based on look in
graphical/CSS browsers.
Personally, I prefer to have main content high/first in the source-code,
as I think main content is the most important part of a web
page/article. Organizing source-code this way gives better separation
between content and presentation, IMO, and one can style it to appear as
one like to anyway.
regards
Georg
--
http://www.gunlaug.no
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
