And of course, you would put any IE specific hacks such as the Holly Hack in an 'ie-hacks' style sheet that would be included in your pages via IE conditional comments.
See http://blogs.msdn.com/ie/archive/2005/10/12/480242.aspx for more info. Ryan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ric Raftis Sent: Saturday, 31 December 2005 4:25 PM To: wsg@webstandardsgroup.org Subject: Re: [WSG] Hi all, need some help with a peekaboo bug in IE - SOLVED G'day Barrie, I think what you need here is called the Holly Hack. It fixes ul, li problems that IE mucks up. CSS for my sites where I use uls include:- /* Fix IE. Hide from IE Mac \*/ * html #navbar ul li { float: left; } * html #navbar ul li a { height: 1%; } /* End */ Reference: http://www.communitymx.com/content/article.cfm?page=2&cid=C37E0 Regards, Ric Barrie North wrote: >How weird, it was being caused by the styles on the ul in the black >main menu box. I don't know why that would shift the whole column, o well. > >Barrie North >Compass Design > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] >On Behalf Of Barrie North >Sent: Friday, December 30, 2005 9:57 PM >To: wsg@webstandardsgroup.org >Subject: [WSG] Hi all, need some help with a peekaboo bug in IE > >I am making a site for IE6+ and am really stuck over an IE bug. > >http://joomlashack.compassdesigns.net/js_jshack06v2/index1.html > >Some strange bug is occurring in IE6, the left column bounces all over. >It seems to be related to the peekaboo bug and you can see it when you >mouse over the links to the left column in the "main menu". Refresh the >page in IE so see the bug again. > >Also, if you click on the "blog" link >http://joomlashack.compassdesigns.net/js_jshack06v2/index1.html >you get a two column layout. For some reason the left column decides it >wants to be in a different place. > >The solutions I know of involve position:relative and height:1% and >line-height:1.2. I have tried all three of these but not had anything work. > >Apologies in advance for not making a page that isolated the bug better. >This is CMS output and I found this bug late in the production cycle... > >Cheers >Barrie North > > >****************************************************** >The discussion list for http://webstandardsgroup.org/ > > See http://webstandardsgroup.org/mail/guidelines.cfm > for some hints on posting to the list & getting help >****************************************************** > > > > > >****************************************************** >The discussion list for http://webstandardsgroup.org/ > > See http://webstandardsgroup.org/mail/guidelines.cfm > for some hints on posting to the list & getting help >****************************************************** > > > > > ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ****************************************************** __________ NOD32 1.1345 (20051230) Information __________ This message was checked by NOD32 Antivirus System. http://www.nod32.com ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
