ansaurus

Question

Answer 1

A:

EDIT

The best way to fix an IE only problem (and there are many IE only problems, esp. in 6+7) is using the "feature" of IE which lets you conditionally include style information only for IE.

Described with an example here: http://dustinbrewer.com/css-trick-target-only-ie-with-an-if-statement/

A prior version of my answer pointed out a "quick fix hack" for IE that would just include one style element in IE. As has been pointed out in the comments there are a lot of reasons not to do it this way, its only positive aspect being that it is quick:

Prior version of answer follows

I would use the IE underscore hack to fix this, here is the first link I found about it:

http://dustinbrewer.com/weekly-css-trick-the-ie-underscore-hack/

Basically you put an underscore before a css attribute and only IE6 and IE7 will use that attribute. So you could do something like _right -34px and it would only effect IE pre version 8.

or in this case change it to have

  padding-left:315px;
  _padding-left:122px;

the first will effect all other browsers and 2nd row will cascade only for IE

Hogan 2010-02-22 01:24:30

-1 for using a hack. Hacks are only acceptable if its the only way to target a browser which is not the case with IE. You should use conditional comments to wrap the specific `style` block or external `link`.

prodigitalson 2010-02-22 01:40:18

One risk of using these hacks is that we'll never know if a future browser will also parse rules hidden by the hack.

Marcel Korpel 2010-02-22 02:07:03

@Marcel ...and if a hack becomes popular and is in widespread use, it may actually hinder the creation of new browsers and/or CSS specs. If the W3C wanted to include a special "underscore syntax" for one reason or another, it probably can't because it would conflict with a popular hack and wreak havoc to many old pages in new browsers that try to follow the new spec. That's more or less how we ended up with the Quirksmode mess.

deceze 2010-02-22 02:15:17

If you add this into external file and include via conditional tags, I don't think will be a problem at all :)

Ionut Staicu 2010-02-22 05:36:22

@deceze: Bullshit. The W3C will never include ‘a special underscore syntax’. Quote from http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords: “An initial dash or underscore is guaranteed never to be used in a property or keyword by any current or future level of CSS.”

Mathias Bynens 2010-03-01 14:44:02

Answer 2

A:

On the surface, your CSS seems fine. Would be useful to see all of your CSS, especially that which applies to body, but it seems to be a parent element problem. Try setting a fixed or percentage width for your div#spotlightHolder.

Tom 2010-02-22 04:24:30

Answer 3

+1 A:

Make sure you don't have any spaces/chars before doctpye declaration.

Also, it may be something about margin collapse (but I can't tell you right now, I just woke up and I'm a more like a zombie right now :D )

However, you didn't tell us if the page is valid. You may also have some nested elements out there. So I think the best thing is to put it online and give us the link :)

Ionut Staicu 2010-02-22 05:41:57

Answer 4

A:

Try Eric Meyer's CSS reset tool instead of wasting your time focusing on IE's quirks.

http://meyerweb.com/eric/tools/css/reset/

And why not assign the 550px width to .spotlightholder so it's inherited?

stillstanding 2010-02-22 22:28:29

Answer 5

A:

I really like blueprint to do css reset.

It Makes getting consistent layout cross browser very easy and is fairly widely used.

Dan Lord 2010-02-22 22:59:39

ansaurus

tags:

views:

answers:

How to overcome IE7 padding issues?

related questions