Re: [css-d] How do you feed IE versions different css than w3c compliant browsers?

On 16/04/2008, James Leslie <[EMAIL PROTECTED]> wrote: > Can anyone explain why you would want to target all non-IE browsers and > then all IE browsers? More realistic example: assume you want to use css 2.1 selectors (those which are supported even by IE7). This makes it necessary to hide the ru

Re: [css-d] How do you feed IE versions different css than w3c compliant browsers?

Nicholas Wilson wrote: > ... > > We have to start with: > > > > Now IE has started a comment, and think > they are not in a comment. In theory, yes. In fact IE erroneously believes that > ...seen by everything except IE... > This is not correct. It is seen by everything, including IE

Re: [css-d] How do you feed IE versions different css than w3c compliant browsers?

On 16/04/2008, Bill Brown <[EMAIL PROTECTED]> wrote: > I could not more *strongly* disagree with you, and I'm not sure why you are > calling my syntax "incorrect" or "unnecessary" either. If they both do the > same thing, mine not only appears (to me, at least) to be more elegant, but > is shorter

Re: [css-d] How do you feed IE versions different css than w3c compliant browsers?

Bill Brown wrote: > Hi John, > > You can use this syntax to target all NON-MSIE browsers: > > @import url("css/fix/non_msie.css"); > > > Use this syntax to target ALL MSIE browsers: > > > And this will target specific versions of MSIE browsers: > > > > CSS in the last three will not be se

Re: [css-d] How do you feed IE versions different css than w3c compliant browsers?

On Wed, 16 Apr 2008 00:27:20 +0200 Manfred Staudinger wrote: > On 15/04/2008, Bill Brown <[EMAIL PROTECTED]> wrote: > > You can use this syntax to target all NON-MSIE browsers: > > > > @import url("css/fix/non_msie.css"); > > > > Thats definitely an unnecessary hack. The correct (although >

Re: [css-d] How do you feed IE versions different css than w3c compliant browsers?

> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > discuss.org] On Behalf Of Nicholas Wilson > Sent: Tuesday, April 15, 2008 5:00 PM > To: css-d@lists.css-discuss.org > Subject: Re: [css-d] How do you feed IE versions different css than w3c &g

Re: [css-d] How do you feed IE versions different css than w3c compliant browsers?

1/ Regarding Conditional Comments, see: Microsoft Developer Network 2/ Regarding using Conditional Comments to feed hacks to IE, see: On havingLayout (scroll down a little to: "Alternatively, and possibly more future proof, are condi

Re: [css-d] How do you feed IE versions different css than w3c compliant browsers?

On Wednesday 16 April 2008 1:09 am John Griessen wrote: > Thierry Koblentz wrote: > > What about a simple: > > > > > > This short one looks good... As I understand this, it goes in default.css, > so what else besides css code would you want to put here? > > John Griessen > css newbie building his

Re: [css-d] How do you feed IE versions different css than w3c compliant browsers?

John Griessen wrote: > Thierry Koblentz wrote: >> > This short one looks good... As I understand this, it goes in default.css, > so what else besides css code > would you want to put here? John: Wrong! It does NOT go in default.css. It is an HTML comment tag...so it goes in your HTML source.

Re: [css-d] How do you feed IE versions different css than w3c compliant browsers?

Thierry Koblentz wrote: > What about a simple: > > This short one looks good... As I understand this, it goes in default.css, so what else besides css code would you want to put here? John Griessen css newbie building his own selling web site. -- Ecosensory Austin TX

Re: [css-d] How do you feed IE versions different css than w3c compliant browsers?

On Wednesday 16 April 2008 12:58 am Thierry Koblentz wrote: > What about a simple: > > > > > Or am I totally missing something here? > > Could be me ;) But then every browser would ignore it, which is presumably not what you want. Nicholas ___

Re: [css-d] How do you feed IE versions different css than w3c compliant browsers?

> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > discuss.org] On Behalf Of Bill Brown > Sent: Tuesday, April 15, 2008 4:27 PM > To: Manfred Staudinger > Cc: css-d@lists.css-discuss.org; John Griessen > Subject: Re: [css-d] How do you feed IE v

Re: [css-d] How do you feed IE versions different css than w3c compliant browsers?

Manfred Staudinger wrote: > On 15/04/2008, Bill Brown <[EMAIL PROTECTED]> wrote: >> You can use this syntax to target all NON-MSIE browsers: >> >> @import url("css/fix/non_msie.css"); >> > > Thats definitely an unnecessary hack. The correct (although > proprietary) syntax would be: > > > c

Re: [css-d] How do you feed IE versions different css than w3c compliant browsers?

On 15/04/2008, Bill Brown <[EMAIL PROTECTED]> wrote: > You can use this syntax to target all NON-MSIE browsers: > > @import url("css/fix/non_msie.css"); > Thats definitely an unnecessary hack. The correct (although proprietary) syntax would be: css here Regards, Manfred ___

Re: [css-d] How do you feed IE versions different css than w3c compliant browsers?

On 15/04/2008, John Griessen <[EMAIL PROTECTED]> wrote: > Manfred Staudinger wrote: > > > Hi John, > > > > If you want to select IE6 and IE7, but not IE8 nor IE5.5 or IE5.01 > > then you might use > > > > > > > > > > Thanks, > > very helpful. Looks like you just put this in line with your stds

Re: [css-d] How do you feed IE versions different css than w3c compliant browsers?

> I have a restructuredtext generated site that now looks as intended in > firefox, but not in the IE > that is installed with Win2K. IE seems to ignore the css positioning of a > list and an image hyperlink. > > http://ecosensory.com/ Hi John, You can use this syntax to target all NON-MSIE b

[css-d] How do you feed IE versions different css than w3c compliant browsers?

David Laakso wrote: > You have height:1%; on the below selector. You may (?) want to feed > that only to IE/6, as compliant browsers might do better without it at > +2 font-scaling. > .p5 { > height: 1%; > } I have a restructuredtext generated site that now looks as intended in firefox, b