W3C home > Mailing lists > Public > www-style@w3.org > September 2011

Re: [CSS21] computed value for percentage 'height'

From: Peter Moulder <peter.moulder@monash.edu>
Date: Sat, 03 Sep 2011 00:09:45 +1000
To: www-style@w3.org
Message-id: <20110902140945.GB11743@bowman.infotech.monash.edu.au>
On Fri, Sep 02, 2011 at 11:10:12AM +0200, Řyvind Stenhaug wrote:
> On Fri, 02 Sep 2011 08:19:31 +0200, Peter Moulder
> <peter.moulder@monash.edu> wrote:
> 
> >Furthermore, when I try to test the behaviour (based on the behaviour of
> >height:inherit in a child), all UAs I've tested inherit the specified
> >percentage rather than 'auto' in this condition.
> 
> Hm, I guess you didn't test Opera.

(I've replied privately re testing Opera.)

Am I right that it only affects the behaviour of height:inherit when
inheriting from a height specified as a percentage even though that
percentage acts like height:auto in other respects?  That sounds like a
very rare case, to the extent that I'd be inclined not to bother
implementing it: I wouldn't expect anyone to notice.

As someone who has implemented it, would you comment on the engineering
cost of the feature?  Am I right that it's a bit tricky when combined
with run-in?  (I haven't been following run-in's development since it was
removed from CSS2.1.)

Is there some authoring benefit to justify the engineering cost?
I'd have thought that authors would be better off if the computed value
were the specified percentage, like most other properties.

pjrm.
Received on Friday, 2 September 2011 14:10:41 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:44 GMT