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,
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
**
Hmmm
This may sound insane, but if the 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:
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
'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 , 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:
>
>
