From: Jeff on
How far back do you have to go lose support for multiple classes:

<p class="class1 class2">

I'm thinking that at this time that this is widely supported. Is that
about right?

I'd like to add this to my bag of tricks.

On a related note, I was working on something that needed a "hack" for
IE5 to keep from being broken. Has IE5 now joined the dustbin of browsers?

Jeff
From: dorayme on
In article <13p4gb0bupe4v92(a)corp.supernews.com>,
Jeff <jeff(a)spam_me_not.com> wrote:

> How far back do you have to go lose support for multiple classes:
>
> <p class="class1 class2">
>
> I'm thinking that at this time that this is widely supported. Is that
> about right?
>

Yes

> I'd like to add this to my bag of tricks.
>
> On a related note, I was working on something that needed a "hack" for
> IE5 to keep from being broken. Has IE5 now joined the dustbin of browsers?
>

Yes

I sometimes have a go at making things nice for MacIE5 but this
is just an entertainment for me. <g>

--
dorayme
From: AGw. (Usenet) on
On Jan 19, 6:28 pm, Jeff <jeff(a)spam_me_not.com> wrote:

> On a related note, I was working on something that needed a "hack" for
> IE5 to keep from being broken. Has IE5 now joined the dustbin of browsers?

If you want to fix something for IE5, I'd suggest that you use
conditional comments; that way, you keep your code (relatively) clean.


--
AGw.
From: Andy Dingley on
On 19 Jan, 18:28, Jeff <jeff(a)spam_me_not.com> wrote:

> <p class="class1 class2">
>
> I'm thinking that at this time that this is widely supported. Is that
> about right?

Yes.

On IE5/Mac it also works, but the parser is fussy about surplus
whitespace: double spaces between classnames, trailing space after the
last classname etc.
From: Harlan Messinger on
dorayme wrote:
> In article <13p4gb0bupe4v92(a)corp.supernews.com>,
> Jeff <jeff(a)spam_me_not.com> wrote:
>
>> How far back do you have to go lose support for multiple classes:
>>
>> <p class="class1 class2">
>>
>> I'm thinking that at this time that this is widely supported. Is that
>> about right?
>>
>
> Yes

As I recall IE6 doesn't handle

.class1.class2 { ... }

correctly--it matches all class1 elements whether or not they have
class2 as well. Is that correct? If so, has IE7 fixed it? I'd check but
I'm not in front of IE7 at the moment.