- From: Simon Fraser <smfr@me.com>
- Date: Wed, 13 Oct 2010 21:46:50 -0700
- To: Sylvain Galineau <sylvaing@microsoft.com>
- Cc: Øyvind Stenhaug <oyvinds@opera.com>, "www-style@w3.org list" <www-style@w3.org>
- Message-id: <510E2AF6-3B69-49AE-BEEF-CDFF22DA529A@me.com>
On Oct 13, 2010, at 8:35 PM, Sylvain Galineau wrote: >> From: www-style-request@w3.org [mailto:www-style-request@w3.org] On >> Behalf Of Øyvind Stenhaug >> Sent: Wednesday, October 13, 2010 5:52 AM >> To: Simon Fraser >> Cc: www-style@w3.org list >> Subject: Re: [css3-3d-transforms] perspective-origin and percentages >> >>> On Oct 12, 2010, at 5:32 pm, Sylvain Galineau wrote: >> >>>> For percentages, the perspective-origin property definition [1] >>>> resolves percentages as: >>>> >>>> # refer to the size of the box itself >>>> >>>> I assume this is identical to transform-origin in 2D Transforms [2]: >>>> >>>> # refer to the size of the element's box >> >> On Wed, 13 Oct 2010 04:43:44 +0200, Simon Fraser <smfr@me.com> wrote: >> >>> That's correct. I'll fix the spec. >> >> Even the definition 2D Transforms spec incorrectly assumes that there's >> just one box per element. >> >> http://lists.w3.org/Archives/Public/www-style/2009Sep/0121.html >> >> -- >> Øyvind Stenhaug >> Core Norway, Opera Software ASA >> > > True. Also not sure 'size' is appropriate here. Does it mean the Y position > percentage refers to the element's height while the X position refers to the > element width ? Or that both refer to width ? Y position refers to height. There was discussion of the behavior of transforms on inlines in the getBoundingClientRect thread. No-one seemed to like Gecko's implementation, but we don't have any better suggestions for how it should work. Until we do, I don't think there's much point expanding on what "box" means for transform-origin and perspective-origin. Simon
Received on Thursday, 14 October 2010 04:48:06 UTC