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

Re: [css3-2d-transforms][cssom-view] Transforming text from the baseline

From: Dean Jackson <dino@apple.com>
Date: Mon, 21 Feb 2011 13:50:58 -0800
Cc: www-style list <www-style@w3.org>
Message-Id: <57FD3B3B-75AB-4D7F-82DC-B4C42D891A1C@apple.com>
To: Jon Rimmer <jon.rimmer@gmail.com>
I think this is an interesting idea, and worth considering. The transform-origin property matchs background-position, so I think the discussion is not limited to transforms.


On Feb 20, 2011, at 2:50 PM, Jon Rimmer wrote:

> I have recently been experimenting with using CSS3 to animate text[1]
> in the manner termed 'kinetic typography'[2]. One problem I've
> encountered is creating transforms whose origin is the baseline of
> some text[3]. While there are workarounds, I think it would be very
> useful if CSS supported declaratively setting a transform's origin to
> be the baseline, and programatically retrieving the position of a
> baseline for an element. I'm not aware if there has already been any
> work in this area, but my proposals would be as follows:
> Allow the transform-origin property to have a value of 'baseline':
> #element {
>   transform-origin: left baseline;
> }
> In the case of an inline-level element, this would cause the origin of
> the transform to be the position of the baseline in the element's
> first inline box. For a block-level element, the origin would be the
> position of the baseline in the first inline box of the block's first
> inline-level element (which might be anonymous). If the block
> contained no inline-level elements at all, it would be equivalent to
> the default value of 50%.
> This could be extended further, to allow specifying other line
> positions such as sub or super, or non-dominant baselines via some
> syntax like baseline(ideographic), but it seems like just allowing
> 'baseline' would cover 99% of the likely use-cases.
> I also propose making it possible to retrieve the baseline position
> via script. I was quite surprised that there did not seem to be a
> standard, non-hacky, way to do this. If there is, and I'm just not
> aware of it, please disregard this. Otherwise, I suggest an additional
> extension to the HTMLElement interface, similar to those already
> defined in the CSSOM View Module. Something like 'baselineOffset'
> that, when called on an element, would return the size of the gap
> between the baseline and the top of the element's first inline box's
> content-area, where the inline box is determined in the same manner as
> described above, and 'top' is whichever edge is appropriate as per
> bidi requirements (which I won't pretend to understand).
> I'm hopeful that, given that the baseline information must already
> exist within layout engines, implementation would not be unreasonably
> hard.
> Any questions? Comments?
> [1] http://www.brillskills.com/fu/ (requires a webkit-based browser)
> [2] http://en.wikipedia.org/wiki/Kinetic_typography
> [3] http://www.brillskills.com/kinetic/
> Jon Rimmer
Received on Monday, 21 February 2011 21:52:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:56 UTC