cc:Mail Link to SMTP Undeliverable Message
Message is undeliverable.
Reason: User "email@example.com" is not found in the cc:Mail Directory.
Original text follows:
Received: from www19.w3.org by met.bitstream.com (ccMail Link to SMTP R8.00.00)
; Mon, 04 Aug 97 12:35:49 -0500
Received: by www19.w3.org (8.8.5/8.6.12) id MAA07240; Mon, 4 Aug 1997 12:26:57 -0400 (EDT)
Resent-Date: Mon, 4 Aug 1997 12:26:57 -0400 (EDT)
From: "Chris Wilson (PSD)" <cwilso@MICROSOFT.com>
To: "'David Perrell'" <firstname.lastname@example.org>, Douglas Rand <email@example.com>
Cc: firstname.lastname@example.org, Todd Fahrner <email@example.com>
Subject: RE: CSS vs. transitional markup [was: No Subject]
Date: Mon, 4 Aug 1997 09:26:18 -0700
X-Mailer: Internet Mail Service (5.0.1458.49)
X-Mailing-List: <firstname.lastname@example.org> archive/latest/2700
Hmm, I think I agree with you, with a slight amendment. I believe
precedence order, from most preferred to least preferred, should go like
HTML attributes & intrinsic HTML element properties (e.g., BLOCKQUOTE is
The change is where HTML properties are handled WRT user stylesheets.
This allows the user greater control.
> -----Original Message-----
> From: David Perrell [SMTP:email@example.com]
> Sent: Friday, August 01, 1997 3:35 PM
> To: Douglas Rand
> Cc: firstname.lastname@example.org; Todd Fahrner
> Subject: Re: CSS vs. transitional markup [was: No Subject]
> Douglas Rand wrote:
> > In our browser, the FONT declarations would override the parent.
> > decls for the FONT tag itself would first be honored, then the
> > attributes. I treat attributes in essentially the same fashion as a
> > STYLE attribute.
> > So my view is that indeed the inline attributes of the FONT should
> > override the parent. For my own implementation it also means that
> > style object associated with FONT and any children's style object
> > inheriting cannot be cached. Ah well.
> You are not in accordance with the spec. From section 3.2, Cascading
> The UA may choose to honor other stylistic HTML attributes, for
> 'ALIGN'. If so, these attributes are translated to the corresponding
> CSS rules with specificity equal to 1. The rules are assumed to be at
> the start of the author style sheet and may be overridden by
> style sheet rules. In a transition phase, this policy will make it
> easier for stylistic attributes to coexist with style sheets.
> Key sentence: "The rules are assumed to be at the start of the author
> style sheet and may be overridden by subsequent style sheet rules."
> IE3.02 is handling inline HTML properties correctly.
> David Perrell