:before and :after content in IE6

Problem example:

http://www.key-horse.com/fftst-content.html

I can't find a workaround for my problem on the web; I can't even find
a report of the problem. But I remember that the problem was discussed
in this group some time ago.

I define two classes, .star2 and .star3, that include content thus:

<style type="text/css">
.star2:before {content: "** "}
.star3:before {content: "***"}
</style>

This works great in FF, but does not work at all in IE 6.0. Is this a
bug in IE 6.0? If so, what's a reasonable workaround, if any?

Thanks!

-- fredo

fredo wrote:

Problem example:

http://www.key-horse.com/fftst-content.html

I can't find a workaround for my problem on the web; I can't even find
a report of the problem. But I remember that the problem was discussed
in this group some time ago.

I define two classes, .star2 and .star3, that include content thus:

style type="text/css"
.star2:before {content: "** "}
.star3:before {content: "***"}
/style

This works great in FF, but does not work at all in IE 6.0. Is this a
bug in IE 6.0? If so, what's a reasonable workaround, if any?

Not sure if I would call it a bug. IE just doesn't support it at all.
The only workaround I know of is just simply writing it in the HTML
instead of in the CSS.

--
Els http://locusmeus.com/
Sonhos vem. Sonhos vão. O resto é imperfeito.
- Renato Russo -
Now playing: David Bowie - Let's Spend The Night Together

Not sure if I would call it a bug. IE just doesn't support it at all.

Thank you.

I would call such an omission a bug of the first water. It renders a
useful CSS feature forever unusable in practice if I want support from
IE; if I want to avoid js; or if I want to serve the smallest html
files. All worthwhile goals, imo.

The IETF asks for reference implementations of a proposed standard. Too
bad something similar couldn't happen with CSS realization in browsers.
Ah, hindsight!

-- fredo

MS never claimed IE6 was a CSS2 browser

Thanks! News to me. As for reference implementations:

Well, there is Amaya and the new Candidate Recommendation (CR) status,
which requires two interoperable implementations to advance. CR was
introduced into the W3C specification process after the publication of
CSS 2.0, but CSS 2.1 uses it.

These implementations will be very useful for all in five years or so.

Thanks for the clarification on IE's claims, Christoph. I appreciate
that.

-- fredo

Christoph said:

Well, there is Amaya and the new Candidate Recommendation (CR) status,
which requires two interoperable implementations to advance.
(...) CSS 2.1 uses it.

Then I said, not entirely ironically:

These implementations will be very useful for all in five years or so.

Christoph replied:

Firefox, Opera and Konqueror/Safari are close to be
interoperable implementations of CSS 2.1 *already*
and all are working to becoming closer.

This is tremendously encouraging. But you've heard it many times
before: I can't make customers use Firefox. Hugely useful CSS features
are lost to me. (Maybe: "best viewed in Konqueror" :-) When the
customer is the audience, we're hostage to the older browsers that
customers want to use. Including IE6.0 five years in the future.

I therefore believe that true compliance and interoperability (what a
beautiful dream!) will benefit me wrt to my customers only after
today's non-compliant browsers have mostly fallen out of use.

We'll see soon what IE7 is.

Yes. One hopes. Thank you again, Christoph, for correcting me on IE6.0
claims. This might mean I'll have to stop bitching about IE6.0. Now
/that/ will be of great, immediate benefit to those who've had to
listen to me :-)

-- fredo

In article <1121051400.005938.266120 (AT) g44g2000cwa (DOT) googlegroups.com>,
"fredo" <fredo (AT) key-horse (DOT) com> wrote:

Yes. One hopes. Thank you again, Christoph, for correcting me on IE6.0
claims. This might mean I'll have to stop bitching about IE6.0. Now
/that/ will be of great, immediate benefit to those who've had to
listen to me :-)

Hell, it seems like just last year that we were bitching about NN4 and
Mac IE5 was top of the line. Things are looking up.

leo

--
<http://web0.greatbasin.net/~leo/

Leonard Blaisdell:

Hell, it seems like just last year that we were bitching about NN4 and
Mac IE5 was top of the line.

Either your memory needs time-adjustment or
your "we" doesn't include me

In truth, it was just last week :-)