W3C home > Mailing lists > Public > public-css-testsuite@w3.org > November 2010

Re: [css3-selectors] What's the point of :empty?

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 3 Nov 2010 13:44:49 +1300
Message-ID: <AANLkTin+0fy1rYw2_1TETD0erKcCj2hbCUuWdNiFynAf@mail.gmail.com>
To: David Hyatt <hyatt@apple.com>
Cc: Rob Crowther <robertc@boogdesign.com>, www-style list <www-style@w3.org>, public-css-testsuite@w3.org
On Wed, Nov 3, 2010 at 11:39 AM, David Hyatt <hyatt@apple.com> wrote:

> Really the sticking point is overflow:hidden, which is commonly used in
> conjunction with text-overflow to truncate content in the inline direction.
> In the vertical direction nothing is clipped.  Think of a button built using
> inline-block that clips/truncates its content horizontally (with ellipses).
>  If you force the baseline to be the bottom margin edge just because
> overflow:hidden was specified, then you can no longer baseline align this
> control.
>
> What the spec says makes sense to me for overflow:auto/scroll, and we could
> change that in WebKit I think, but there's a problem with what is specified
> for overflow:hidden.
>

Sounds like what you really want is overflow-x:hidden, overflow-y:visible
... with the baseline behavior depending only on overflow-y.

Rob
-- 
"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]
Received on Wednesday, 3 November 2010 00:45:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 3 November 2010 00:45:35 GMT