|
spitfire -> RE: CSS Layout Problem in IE (6/10/2006 19:36:06)
|
quote:
ORIGINAL: boonedawg I do, would you be so kind as to point them out to me? They are: quote:
URI : http://www.ramare.com/scripts/pageStyles2.css Line: 247 Context : .2CO In CSS1, a class name could start with a digit (".55ft"), unless it was a dimension (".55in"). In CSS2, such classes are parsed as unknown dimensions (to allow for future additions of new units) : To make ".2CO" a valid class, CSS2 requires the first digit to be escaped (".\32CO") URI : http://www.ramare.com/scripts/navStyles.css Line: 45 Context : #navcontainer ul li a Invalid number : background Too many values or values are not recognized : transparent url(../imgs/mb.gif) 5px center no-repeat Line: 55 Context : #navcontainer ul li a:hover Invalid number : background Too many values or values are not recognized : transparent url(../imgs/mb2.gif) 5px center no-repeat Line: 61 Context : #navcontainer ul li a#current Invalid number : background Too many values or values are not recognized : transparent url(../imgs/mb2.gif) 5px center no-repeat But I am not entirely convinced any of them have anything to do with the structure of the page. You have done a lot of work on this and made a number of changes but you do not appear to have put your latest version on line. So, would you be prepared to go a few steps further? 1) If you do not already have it, download the Fx Web Developer Toolbar. Then select "outline" and "block level elements". Look at how the divs abut each other very closely. IE doesn't like this much and tends to squidge things all over the place. 2) Down load the IE Accessibility Toolbar (best NOT to use the newish Microsoft one yet/until it gets bedded in). Then select "structure" and "show divs". The extent of IE's squidging becomes apparent. [:@] 4) Now consider the math (going from the online version at this moment) and add up the widths of everything that you want in #container, #content etc. Don't forget margins/padding etc just for IE's benefit. Doesn't quite fit. 5) You could try closing the header div after .headnav. It appears to work for IE and seems to have no effect on Fx BUT you will have the existing (extra) closing div after #newproductscontent . If you close it, it will mess up your "Stay informed" area. If you leave it there you will get a validator error, if that means a lot to you. It's a fudge (forced by the existing page layout you have, or have been given, which isn't really cross-browser friendly) but, hey it's a workable fudge.[:D] It looks like it is shaping up into a good looking site and worth keeping plugging away at.[;)]
|
|
|
|