Re: [css3-values][css3-background][css3-transforms] <position> vs. transform-origin

On Sat, Mar 23, 2013 at 9:52 AM, Simon Sapin <> wrote:
> Le 20/03/2013 23:11, Tab Atkins Jr. a écrit :
>> On Wed, Mar 20, 2013 at 7:23 AM, Øyvind Stenhaug <>
>> wrote:
>>> The transform-origin value type is different from that of
>>> background-position in that a third component value represents a position
>>> on
>>> the Z-axis rather than an offset to a preceding percentage/keyword.
>>> (<> has a
>>> resolution concerning this.)
>> I wish we could solve this. :/  The grammatical ambiguity is annoying.
>>   It would probably be worthwhile to define a <3d-position> type,
>> though, that just matches transform-origin's current grammar.
> Using '<position> <length>?' would be ambiguous, right? Even with tricks
> like "parsing <position> should consume as many tokens as possible"?

With a trick like that, it's not ambiguous.  But we try to avoid those
kinds of things when possible.

More importantly, specifying something like that wouldn't be backwards

>>> That difference doesn't apply to perspective-origin, though, so that does
>>> seem to be an issue. Has been reported earlier here:
>> Looks like it got forgotten in the craziness of that thread.  It would
>> indeed be nice (and backwards-compatible) to upgrade
>> perspective-origin to a <position>.
> I read half of that thread but I’ll probably stop here :)
> Can we ask in the next conf call to have perspective-origin reference Values
> 3 for <position>, and leave the discussion of what <position> should be for
> another time?

It's an editorial change, but it would probably be nice to inform the
WG anyway. ^_^


Received on Saturday, 23 March 2013 21:36:35 UTC