Re: inline-block baseline when the baseline would be outside of the element

Doh, right, so that wasn't 100% helpful after all. :) I guess what's
interesting is what goes on in the block progression direction,
overflow-wise. Whatever happens to inline overflow probably isn't
interesting at all, right?

Then again, there's also a different defintion of overflow-x and
overflow-y in a different spec - here:

This one is closer to what the browsers actually have implemented (if we
ignore prefixed 'paged-*' values in Webkit and Presto), and here the
computed values are required to agree on being either visible or
non-visible. With this spec it's straight-forward to do what the last
paragraph in chapter 10 of the CSS 2.1 spec says.

Christian Biesinger <> writes:

> Hm... that seems to be only mostly true. For the fragmenting values,
> it seems to be possible to have visible and non-visible:
> "If one of the cascaded values is one of the fragmenting values and
> the other is not, then the computed values are the same as the
> cascaded values."
> Although Chrome doesn't seem to implement that and converts visible to
> auto when I use -webkit-paged-x...
> -christian
> On Thu, Jul 11, 2013 at 4:42 AM, Morten Stenshorne <> wrote:
>> Christian Biesinger <> writes:
>>> On Wed, Jul 10, 2013 at 11:24 AM, Boris Zbarsky <> wrote:
>>>> On 7/10/13 11:20 AM, Christian Biesinger wrote:
>>>>> PS: I just realized that in Firefox, if I add overflow: hidden;, then
>>>>> the baseline changes! In other words: the overflow setting affects the
>>>>> positioning of the box. That also seems weird?
>>>> From last paragraph:
>>>>   The baseline of an 'inline-block' is the baseline of its last line
>>>>   box in the normal flow, unless it has either no in-flow line boxes or
>>>>   if its 'overflow' property has a computed value other than 'visible',
>>>>   in which case the baseline is the bottom margin edge.
>>>> The fact that WebKit does not do that is a longstanding issue in WebKit.
>>> I guess I'm supposed to interpret that as "either overflow-x or
>>> overflow-y is not visible"...?
>> It doesn't really matter. It's enough to check one, since it's
>> impossible to have the computed value of one of them be visible and the
>> other non-visible.

---- Morten Stenshorne, developer, Opera Software ASA ----
---- Office: +47 23692400 ------ Mobile: +47 93440112 ----
------------------ -----------------

Received on Thursday, 11 July 2013 16:38:53 UTC