Re: [WSG] IE7 Compatibility Team

[Kenneth Fraser]

Greetings,

From my experience when I run into an IE bug (double-margin / 3 pixel 
jog) that could use height: 1% to fix it, I use display: inline as an 
alternative and it saves a hack in your code or one less reason to use a 
conditional comment. I haven't noticed any problems with other browsers 
using this and I test on around 10 of them. Perhaps I haven't seen the 
particular scenario yet but I think the height: 1% fix can safely be 
tucked under a rug.


Later days,
Kenneth

Lachlan Hunt wrote:

Cade Whitbourn wrote:

The compatibility issue is caused by our use of CSS filters. They
specificially highlight our use of Star HTML Hack, Selector HTML Hack
and the Holly Hack.


I'm not sure what you mean by the Selector HTML Hack.

The problem with the * html filter is that they removed it without 
solving all the limitations it's required for.  However, removing it 
was the right move to make, because now that * html is removed from 
IE7, it does make it completely safe to use for targeting IE6 and 
earlier, you just need to sort out which limitations are still 
present, and thus which patches are still required to be applied and 
find an alternate filter to use.


Personally, I rarely use anything but the holly hack:

  * html foo { height: 1%; }

And it turns out that for the one site I've fixed up, all I had to do 
was remove most occurences of it from throughout my stylesheet and 
move them all to an additional stylesheet which is now imported using 
a conditional comment


!--[if lte IE 7]link rel=stylesheet type=text/css 
href=/style/iehacks.css![endif]--


For example, I had many occurrences like this scattered throughout:
  * html foo { height: 1%; }
  * html bar { height: 1%; }
  * html baz { height: 1%; }

Now, in iehacks.css, I have:

foo, bar, baz { height: 1%; }

It does make it a little cleaner and effectively makes the other 
stylesheets hack free (except for the display:inline; patch to fix 
double-margin float bugs and 1 or 2 IE6 only bugs applied with * html)



(I would like to just quote the email verbatim but it's headlined
**Microsoft Confidential** which makes me nervous - even though there's
no confidential information in the email that I can see).


Such things are thrown into many corporate e-mails for no other reason 
than unjustified paranoia, I'm sure no-one would mind if you quoted it 
fully.  It sounds like they're probably sending the same template 
e-mail to hundreds of sites (just customising it to mention specific 
hacks).




**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**

Re: [WSG] suckerfish menu and position:relative woes

[Kenneth Fraser]

Hi Pete,

I had the same issue before and had to add one line to the js code for 
the drop-downs to hover on top. The extra line is commented.


Hope this helps,
Kenneth

startList = function() {
if (document.alldocument.getElementById) {
navRoot = document.getElementById(nav);
for (i=0; inavRoot.childNodes.length; i++) {
node = navRoot.childNodes[i];
if (node.nodeName==LI) {
node.onmouseover=function() {
this.className+= over;
this.style.zIndex=200; //Add this line to your JavaScript Code
 }
 node.onmouseout=function() {
 this.className=this.className.replace( over, );
  }
  }
 }
}
}
window.onload=startList;

Peter Ottery wrote:

hiya,
i dont like flyout menus as much as the next guy/girl but i have a
situation that requires them, so i'm using the son of suckerfish menu
[1].

i'm having a problem with adding position:relative to items below the
menu, and those elements appearing on top of the flyout menus in IE.
i've whipped up a barebones example with further explanation here:
http://skunkworks.farcrycms.com/pot/temp/test.html
the css  js is wihtin the head of that page to allow easy copy  pasting.

as that page details, anyone got a tip that allows me to keep
position:relative on that box but keeps the flyout menus on top (when
they flyout) ?

any help appreciated, cheers , pete

[1] = http://www.htmldog.com/articles/suckerfish/dropdowns/
**
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
**

Re: [WSG] suckerfish menu and position:relative woes

[Kenneth Fraser]

No problem Pete, glad to be of service.

The fix comes from an article by Nick Rigby that I found while trying to 
figure out the same problem you had. You can read the article at 
http://www.nickrigby.com/article/25/drop-down-menus-horizontal-style-pt-3. 
The line of javascript is mentioned by him somewhere in the comments 
after someone reporting the same issue.


Later days,
Kenneth

**
The discussion list for  http://webstandardsgroup.org/

See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list  getting help
**