W3C home > Mailing lists > Public > www-style@w3.org > February 2015

Re: [css-align][css-inline] First/last baseline alignment

From: Brad Kemper <brad.kemper@gmail.com>
Date: Tue, 24 Feb 2015 15:43:21 -0800
Cc: "www-style@w3.org" <www-style@w3.org>
Message-Id: <533AA37E-35CA-4FDE-A768-506D0C81449D@gmail.com>
To: Javier Fernandez <jfernandez@igalia.com>

> On Feb 24, 2015, at 3:56 AM, Javier Fernandez <jfernandez@igalia.com> wrote:
> 
> Hi,
> 
>> On 02/24/2015 05:01 AM, fantasai wrote:
>> 
>>  <baseline> = [ first | last ]? && baseline
>> 
>> instead of
>> 
>>  <baseline> = baseline | first-baseline | last-baseline
> 
> Separate keys complicates CSS parsing. Even though it's not terribly
> complex, I fail to see the advantages of having separate keywords. I
> think the second form is clearer.

I was primarily thinking about inline-vertical alignment, but I can see the point of not having vertical alignment in row structures be too different. 

So my take would be something more like this: 

<line-based> = [ first | last ]? && [ baseline | text-top | text-bottom | middle | central ]?

So that you could do 'vertical-align: first middle', for instance. 

So that would be the advantage. I realize now (that I've read more of these specs) that the bigger advantage of being able to align to the top baseline of an inline-block could be provided by 'first-baseline', and that's great. This variation could provide a bit more power that I think would be useful. 

If we think we will never go this way, even in a future version, then leave the dash in. Otherwise, I'd use a space instead. 
Received on Tuesday, 24 February 2015 23:43:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:52:01 UTC