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

Re: Multiple baseline question

From: L. David Baron <dbaron@dbaron.org>
Date: Mon, 23 Jul 2012 17:11:00 -0700
To: Julien Chaffraix <julien.chaffraix@gmail.com>
Cc: www-style@w3.org, robert@webkit.org
Message-ID: <20120724001100.GA31116@crum.dbaron.org>
On Monday 2012-07-23 16:32 -0700, Julien Chaffraix wrote:
> I have a question about the attached test-case. This is question
> related to a recent change in WebKit where we aligned our table
> baseline computation with CSS 2.1 but changed the output of the test.
> Longer context can be found here:
> https://bugs.webkit.org/show_bug.cgi?id=91137
> 
> Browsers don't agree on the exact behavior in this case:
> * WebKit (after the change) / Opera don't horizontally align the 2 rectangles.
> * WebKit (before the change) / FF and IE align them.
> 
> The current line of thoughts is that the 2 inline-blocks shouldn't be
> vertically aligned:
> * We align the 2 inline-blocks along their baseline as vertical-align
> defaults to 'baseline'.
> * "The baseline of an 'inline-block' is the baseline of its last line
> box in the normal flow", which means that the inline-block baseline is
> the anonymous inline-table's.
> * "The baseline of an 'inline-table' is the baseline of the first row
> of the table."
> * "If a row has no cell box aligned to its baseline, the baseline of
> that row is the bottom content edge of the lowest cell in the row.",
> the only table cell's has vertical-align: middle so the baseline of
> the row is the bottom of the content edge.
> 
> Let me know if our interpretation is right or if we missed something.

I believe it is correct, and has been since the resolution of CSS
2.1 issue 26, but I might be missing something.

I think the relevant Gecko bug is
https://bugzilla.mozilla.org/show_bug.cgi?id=569645 .  (Note that
the relationship of this issue to CSS 2.1 issue 26 is not a question
of whether we should have resolved issue 26 at all (where all
browsers agreed), but rather in which one of two possible ways we
should have resolved it (where browsers disagreed). [1])

However, based on the information in that Gecko bug, I would have
expected IE's behavior to be different.  This suggests that there
may be Web-compatibility implications to the choice discussed in
[1], and it might need to be reconsidered.

I think it would be useful if somebody could explain why IE aligns
the two boxes.  That might point to something we're missing.

-David

[1] for more details, see the part of
    http://lists.w3.org/Archives/Public/www-style/2010Apr/0273.html
    starting with "http://wiki.csswg.org/spec/css2.1#issue-26"

-- 
𝄞   L. David Baron                         http://dbaron.org/   𝄂
𝄢   Mozilla                           http://www.mozilla.org/   𝄂
Received on Tuesday, 24 July 2012 00:11:24 GMT

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