CSS class IE Incompatability

Assembled / ASSEMBLED
July 2, 2010 at 22:49:06
Specs: Vista Ultimate, E6550, 4GB DDR2
The following code (html and css) work fine in Firefox and in Safari
color: red;
color: green;
color: blue;
color: brown;

He owns a <car class="maruti">maruti</car> car
He owns a <car class="swift">swift</car> car
He owns a <car class="honda">Honda </car>car
He owns a <car>car</car>

However, when I open this same file in Internet Explorer, then all the words are black, there is no color at all. Is this not supposed to work in IE? Is there another way to create something similar in IE where I can create my own tags and own classes in IE?


See More: CSS class IE Incompatability

Report •

July 3, 2010 at 00:35:03
Nope, IE won't work with custom elements like that. You can make whatever CSS classes you want, though.

You could, maybe, use a javascript XML converter or something to provide this, but it would be a pain.

And the proper way to translate XML data into another format would be to use XSLT ( xml+xslt -> xhtml )

Report •

July 4, 2010 at 00:19:45
I don't know much about xml (yet). Just getting familiar with the basics like CSS for now.

I think still IE has about 60% market share among all the browsers or so, so it's better to always design for IE.


Report •

July 4, 2010 at 14:31:38
Yep, you're right about 60 % market share. But IE is so godawfully broken, it's hard to do anything cool with it.

I don't agree with Designing for IE, though.

IE has been f---ing up the Web for so long, I WANT my pages to look bad in IE, as long as they're still USABLE.

I design for Firefox, & webkit browsers, and browsers that actually bother to follow the standards.

Then I go back & fix big problems in IE, or use something like: ie6update to popup a message saying "Your browser is missing updates..." To get them up to a newer version.

But, don't bend over to IE. The days of IE dominating everything are slowly fading away, and we need to ENCOURAGE that.

Report •

Related Solutions

July 6, 2010 at 02:53:13
One of the counter arguments I read was that IE helps keeps things in check. By not supporting every new standard as soon as it is released, IE is actually keeping things orderly. In fact, one of the authors that I read said that because IE stuck to their guns and did not implement support for any and every new feature that was made available, that is why we have some standards in web design today.

But I do agree with you, it is frustrating to see that Safari and Firefox work beautifully with some features, but IE will refuse to support them.


Report •

July 8, 2010 at 04:38:31
Hi again,

What I am doing is previewing all the code in Firefox, IE and Safari. I am noticing lot of incompatibilities.

1) Would you recommend to avoid using frames in sites?
Actually, I have not been able to get the results I wanted using this tag, so I am going to give it a pass anyway.

2) I could get the results i wanted with <iframe> but it behaved one way in IE and safari, and it behaved differently in FF. In FF the image inside the iframe scaled down to the size of the <iframe>. But in IE and safari the imaged did not scale down, but instead horizontal and vertical browsers were offered.

What do experienced designers suggest learners should do with such cases? Should I just ignore the tags like <frameset> and <iframe> anyway and stick to the tags that behave the same in all browsers?


Report •

Ask Question