Re: [WSG] Connditional Comment / @import Problem in IE 5.0.1
Andrew Krespanis wrote:
This may sound insane, but if the style element is adding whitespace, try
style {
display:none;
}
I've never heard of this before, but my suggestion could be worth a try...
I gave the display and height properties a shit with no luck. I've never
heard of anything like this either and it's really weird that it happens
in IE 5.0.1, but not 5.5.
I'm guessing you're using the @import method to hide styles from NN4?
Yes, and if I can't figure out what the deal is, I suppose I'll @import
within a linked stylesheet--I just hate having to use that kind of system.
Thanks for the reply.
--
Best regards,
Michael Wilson
**
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] Connditional Comment / @import Problem in IE 5.0.1
Kay Smoljak wrote: I've seen something similar when the conditional comment syntax wasn't quite right. The way they handle GT and LT is a little odd... I'd check what you have against MSDN. Hi Kay MSDN calls for !--[if expression] HTML ![endif]--, which is what I am using. And... since I'm just stating [if IE], this really shouldn't be isolated to IE 5.0.1. I did a little more testing and things get stranger. IE 5.0.1 breaks when I use: style type=text/css @import url(css/iqmax.css); /style !--[if IE] link href=css/iqmax.ie.css rel=stylesheet type=text/css / ![endif]-- If I change the method to: style type=text/css @import url(css/iqmax.css); /style !--[if IE] style type=text/css @import url(css/iqmax.ie.css); /style ![endif]-- ...it works like a champ. I suppose this will work just dandy, but I'm still baffled as to why the previous method is causing problems. My only guess is that the problem is tied directly to something in my markup. I've used this same method several times recently (01), with no problems at all. Unless there is something screwy with my link... syntax that I'm missing, I suppose it will have to remain a mystery. 01: http://www.iqmax.com/iqtray/memCardSync.htm -- Best regards, Michael Wilson ** 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] Connditional Comment / @import Problem in IE 5.0.1
MSDN calls for !--[if expression] HTML ![endif]--, which is what I am using. And... since I'm just stating [if IE], this really shouldn't be isolated to IE 5.0.1. Its preferable to use !--[if lt IE7] instead, as there's a pretty strong chance that the real IE7 will obey standards Oh, and if a website (or user) employs the IE7 JavaScript library, then it will treat conditional comments as though it were the real IE7. -- -David R ** 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] Connditional Comment / @import Problem in IE 5.0.1
David R wrote: MSDN calls for !--[if expression] HTML ![endif]--, which is what I am using. And... since I'm just stating [if IE], this really shouldn't be isolated to IE 5.0.1. Its preferable to use !--[if lt IE7] instead, as there's a pretty strong chance that the real IE7 will obey standards I agree there is a chance that my conditional could mess with IE 7... when we finally see it--*if* we finally see it. At this point though, all MS released versions of IE need the selectors in this particular stylesheet and I don't have any basis to believe IE7 will not. There aren't any hacks in the conditional stylesheet, but it does correct a slight rendering difference between IE and... well, everything else. I think I'll stick with [if IE] for now and see what gives when IE 7 is released--it may not be an issue that gets corrected and if it does, I'll catch it for sure. Oh, and if a website (or user) employs the IE7 JavaScript library, then it will treat conditional comments as though it were the real IE7. I haven't really given much thought to a *user* implementing the IE7 JavaScript hacks. I suppose there is some merit in considering this possibility, but given our users, I'd say the chances of this being the case are extremely remote. I haven't checked to see if this particular issue is evident in any user implementation of IE7, but I will look into it. Thanks for the comments. -- Best regards, Michael Wilson ** 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] Connditional Comment / @import Problem in IE 5.0.1
On Mon, 10 Jan 2005 10:31:02 -0500, Michael Wilson [EMAIL PROTECTED] wrote: I did a little more testing and things get stranger. IE 5.0.1 breaks when I use: Hmm... you said you're using the standalone IE versions, right? I'd test in a real IE 5.01 before you write it off completely if I were you... those standalone versions are very, very confused about their identities :) -- Kay Smoljak http://kay.smoljak.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 **
Re: [WSG] Connditional Comment / @import Problem in IE 5.0.1
Kay Smoljak wrote: Michael Wilson wrote: I did a little more testing and things get stranger. IE 5.0.1 breaks when I use: Hmm... you said you're using the standalone IE versions, right? I'd test in a real IE 5.01 before you write it off completely if I were you... those standalone versions are very, very confused about their identities :) I don't have a test machine with IE 5 loaded, but again, given that I am saying [if IE]--no version specified--I think the chances of it being some kind of standalone quirk are slim. Not impossible though and if I were using some other condition, I might give it a little more weight. The fix I came up with is good enough, but if someone has a full install of IE 5.0.1 on Windows, I'd appreciate a hit to a test page just to see if that's the case. -- Best regards, M. Wilson ** 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] Connditional Comment / @import Problem in IE 5.0.1
On Mon, 10 Jan 2005 23:22:26 -0500, Michael Wilson [EMAIL PROTECTED] wrote: I don't have a test machine with IE 5 loaded, but again, given that I am saying [if IE]--no version specified--I think the chances of it being some kind of standalone quirk are slim. Personally I wouldn't trust the standalone versions to be accurate for anything. I have a Virtual PC image with Windows 98 SE and IE 5.00.2614.3500 and Windows 2000 with IE 5.50.4134.0600 - but no 5.01, unfortunately. If you'd like me to take some screenshots anyway just send the link. Cheers, K. -- Kay Smoljak http://kay.smoljak.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 **
Re: [WSG] Connditional Comment / @import Problem in IE 5.0.1
Hmmm
This may sound insane, but if the style element is adding whitespace, try
style {
display:none;
}
in the IE 5.0 styles.
If that stops the style element from working (?), try height:1px;
I've never heard of this before, but my suggestion could be worth a try...
I'm guessing you're using the @import method to hide styles from NN4?
If so, this will also work:
link rel=stylesheet type=text/css media=screen,projection /
While it's totally valid, NN4 can't handle multiple media values and
ignores the CSS.
I noticed you also use quotes in the @import command to hide from
IEmac. If you put an @import rule inside a CSS file which is
link'ed, you will avoid your IE5 space problem and still hide the
CSS from IEmac and NN4.
Hope that helps :)
Andrew.
http://leftjustified.net/
On Fri, 07 Jan 2005 15:48:22 -0500, Michael Wilson [EMAIL PROTECTED] wrote:
Hi all,
I sent this earlier, but I think I accidentally hijacked another post...
For quite a while, I've been using my spare time to improve the
standards, CSS, usability, and accessibility of one of my projects. In
doing so I've also been trying to move away from IE hacks in my CSS in
favor of conditional comments, which for the most part has been a fairly
seamless process.
While making some adjustments to the main template (01) this morning, I
noticed IE 5.0.1 would behaving oddly when I added a particular
conditional comment. When I included the conditional comment, a rather
large gap would appear at the top of the page. At first, I thought
something in the IE stylesheet was causing the problem, but after
further testing I realized that it was the comment itself that caused
the issue, or rather, the comments position in the markup.
If I place the comment above the @import (02) of my main stylesheet,
everything seems to work fine; however, there is a single selector in
the IE specific stylesheet that needs to override a selector in the main
stylesheet, so the conditional comment *has* to come after the @import.
When I move the comment below the @import, IE 5.0.1 (not 5.5 or 6.0)
breaks (03).
I can completely remove the CSS from the IE specific stylesheet--saving
it as a blank document-- and the problem persists. Furthermore, and this
just makes things weirder, if I use a link href=.../, rather than
@import, the problem vanishes. I also tested several other import
methods, all of which, produce the same results as the method I
originally used.
I am using the hacked, standalone versions of IE 5.0.1 and 5.5 for
testing; however, I am aware of the issues with using conditional
comments. This particular conditional uses [if IE], so the version of IE
*should be* irrelevant. I only mention this to be sure all my conditions
are straight, in case there is any question.
Has anyone ever experienced something similar to this issue or know of
any documentation that might help explain it? Of course, I could just be
doing something stupid or overlooking something simple. I'll leave the
comment in the broken position for now, so y'all can check it out if
you like.
01: http://www.iqmax.com/iqmaxcss/
02: http://www.iqmax.com/downloads/mike/beforeimport.gif
03: http://www.iqmax.com/downloads/mike/afterimport.gif
@import method used:
style type=text/css
!--
@import url(css/iqmax.css);
--
/style
Conditional comment used:
!--[if IE]
link rel=stylesheet type=text/css href=css/iqmax.ie.css /
![endif]--
--
Best regards,
Michael Wilson
**
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] Connditional Comment / @import Problem in IE 5.0.1
On Fri, 07 Jan 2005 15:48:22 -0500, Michael Wilson [EMAIL PROTECTED] wrote: When I included the conditional comment, a rather large gap would appear at the top of the page. At first, I thought something in the IE stylesheet was causing the problem, snip I've seen something similar when the conditional comment syntax wasn't quite right. The way they handle GT and LT is a little odd... I'd check what you have against MSDN. -- Kay Smoljak http://kay.smoljak.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 **
[WSG] Connditional Comment / @import Problem in IE 5.0.1
Hi all, For quite a while, I've been using my spare time to improve the standards, CSS, usability, and accessibility of one of my projects. In doing so I've also been trying to move away from IE hacks in my CSS in favor of conditional comments, which for the most part has been a fairly seamless process. While making some adjustments to the main template (01) this morning, I noticed IE 5.0.1 would behaving oddly when I added a particular conditional comment. When I included the conditional comment, a rather large gap would appear at the top of the page. At first, I thought something in the IE stylesheet was causing the problem, but after further testing I realized that it was the comment itself that caused the issue, or rather, the comments position in the markup. If I place the comment above the @import (02) of my main stylesheet, everything seems to work fine; however, there is a single selector in the IE specific stylesheet that needs to override a selector in the main stylesheet, so the conditional comment *has* to come after the @import. When I move the comment below the @import, IE 5.0.1 (not 5.5 or 6.0) breaks (03). I can completely remove the CSS from the IE specific stylesheet--saving it as a blank document-- and the problem persists. Furthermore, and this just makes things weirder, if I use a link href=.../, rather than @import, the problem vanishes. I also tested several other import methods, all of which, produce the same results as the method I originally used. I am using the hacked, standalone versions of IE 5.0.1 and 5.5 for testing; however, I am aware of the issues with using conditional comments. This particular conditional uses [if IE], so the version of IE *should be* irrelevant. I only mention this to be sure all my conditions are straight, in case there is any question. Has anyone ever experienced something similar to this issue or know of any documentation that might help explain it? Of course, I could just be doing something stupid or overlooking something simple. I'll leave the comment in the broken position for now, so y'all can check it out if you like. 01: http://www.iqmax.com/iqmaxcss/ 02: http://www.iqmax.com/downloads/mike/beforeimport.gif 03: http://www.iqmax.com/downloads/mike/afterimport.gif @import method used: style type=text/css !-- @import url(css/iqmax.css); -- /style Conditional comment used: !--[if IE] link rel=stylesheet type=text/css href=css/iqmax.ie.css / ![endif]-- -- Best regards, Michael Wilson ** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list getting help **
