W3C home > Mailing lists > Public > www-style@w3.org > January 2014

Re: [css-gcpm][css-figures] float-offset & line rhythms

From: Brad Kemper <brad.kemper@gmail.com>
Date: Sat, 25 Jan 2014 21:45:03 -0800
Message-Id: <E8D25750-8645-4049-9311-3B98FAC25264@gmail.com>
Cc: "liam@w3.org" <liam@w3.org>, HÃ¥kon Wium Lie <howcome@opera.com>, Alan Stearns <stearns@adobe.com>, "robert@ocallahan.org" <robert@ocallahan.org>, "www-style@w3.org" <www-style@w3.org>
To: "Cramer, Dave" <Dave.Cramer@hbgusa.com>
On Jan 25, 2014, at 8:51 PM, "Cramer, Dave" <Dave.Cramer@hbgusa.com> wrote:

>> Note, I'd expect marginalia, initial caps, figure boxes etc. also to
>> align to the baseline grid - and, if appropriate, running headers and
>> footers.
> 
> Yes. Initial caps are a particular problem in CSS, which I believe should
> be addressed, but that's another topic.

I think it would still fit in with this idea. Floated elements still have a baseline, so ideally it should still align with the other lines in the parent block. It should automatically move downward until it finds a baseline to align with in its parent block (I think I'd do the same with table cell contents if there is a block ancestor with a non-'auto' 'linespacing' value). Then if you wanted to move it up a line or two, you could use relative positioning, negative margin, or translate() to move it vertically from where 'linespacing' would put it (a line height unit would be useful here). Positioning and margin and transforms (and vertical-align on inline elements) should be allowed to break the rhythm, if the author desired, by nudging it away from the baseline in arbitrary amounts.
Received on Sunday, 26 January 2014 05:45:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:39 UTC