Click to See Complete Forum and Search --> : Is it the IE hack which is causing my parse error?


Dopple
09-13-2006, 07:04 AM
I have the following showing up as an error when I validate. Can anyone tell me why this is? the 2 #menu styles didn't show up until I used the IE hack on them. But why are only some of the hacks showing up when others seem to be accepted? Is there a probnlem with the actual styles or is this just because of the hack?
Line: 92 Context : *
Parse Error - *html #menu ul { margin:0; padding:14px 3px 3px 5px; list-style:none outside; }

Line: 95 Context : *
Parse Error - *html #menu ul li { margin: 0 0 8px 0; }

Line: 168 Context : *
Parse Error - *html #scrollerpar { position:absolute; border:0; width:256px; top:590px; height:65px; left:205px; z-index:1; }

Line: 214 Context : *
Parse Error - *html #scroller { position:absolute; top:555px; border: 0; width:100%; padding:0; margin:0; z-index:3; }

WebJoel
09-13-2006, 07:51 AM
re:
Parse Error - *html #menu ul { margin:0; padding:14px 3px 3px 5px; list-style:none outside; }
etc., -why do you need to declare "html" before "#menu ul" for the 'hack'? That is rather broad. I'm just curious here. -It is somewhat unusual to see "html" in addition to anything besides "body", the two being imho loosely synomomous (the 'body' being html and the html is how the body is written). Try removing "html" from "*html #menu ul" (and instances thereof) and see if anything changes.. It is possible this 'hacking' is affecting more than just "#menu ul" et~al (but I don't know, -I don't get to work with 'hacks' much).

Dopple
09-13-2006, 07:56 AM
I have
#menu ul{} - which is for the standards compliant browsers
&
*html #menu ul {} - which is where I put the code for IE to display correctly.

Firefox and other browsers will ignore the code with *html in front of it.