W3C home > Mailing lists > Public > www-style@w3.org > May 2012

RE: Mandate longhand naming conventions and [css3-text] text-emphasis-position

From: Koji Ishii <kojiishi@gluesoft.co.jp>
Date: Fri, 4 May 2012 15:51:34 -0400
To: Lea Verou <leaverou@gmail.com>, Florian Rivoal <florianr@opera.com>
CC: "www-style@w3.org" <www-style@w3.org>
Message-ID: <A592E245B36A8949BDB0A302B375FB4E0D3C3C804C@MAILR001.mail.lan>
text-underline-position[1] too.

> Example 21
> Because ‘text-underline-position’ inherits,
> and is not reset by the ‘text-decoration’ shorthand,

For these two properties, I think the current design works better than either making it part of shorthand or changing the property names.

While your general idea seems to make sense, I think authors would surprise if
  :root { text-emphasis-position: below right; }
  span.r { text-emphasis: red; }
changes position, wouldn't they?

[1] http://dev.w3.org/csswg/css3-text/#text-underline-position


-----Original Message-----
From: Lea Verou [mailto:leaverou@gmail.com] 
Sent: Friday, May 04, 2012 10:49 PM
To: Florian Rivoal
Cc: www-style@w3.org
Subject: Re: Mandate longhand naming conventions and [css3-text] text-emphasis-position

On 4/5/12 16:24, Florian Rivoal wrote:
> We haven't resolved on that so far, but I've found one more property 
> that doesn't follow the convention that all foo-* properties should be 
> longhands of foo:
> text-emphasis-position is not a longhand of text-emphasis. The specs 
> says so explicitly, and gives a good rationale for it.
> http://dev.w3.org/csswg/css3-text/#text-emphasis-position

> If we end up adopting the convention as an official rule, we need to 
> either agree to make an exception here, or to rename the property.
>  - Florian
I also discovered another one: animation-play-state http://www.w3.org/TR/css3-animations/#animation-play-state-property

Lea Verou (http://lea.verou.me | @LeaVerou)

Received on Friday, 4 May 2012 19:52:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:15 UTC