- From: Simon Fraser <smfr@me.com>
- Date: Tue, 31 Aug 2010 09:19:48 -0700
- To: Brad Kemper <brad.kemper@gmail.com>
- Cc: Boris Zbarsky <bzbarsky@MIT.EDU>, www-style list <www-style@w3.org>
On Aug 31, 2010, at 8:52 am, Brad Kemper wrote: > On Aug 31, 2010, at 8:44 AM, Simon Fraser wrote: > >>> For what it's worth, Gecko's behavior here is to determine a separate transform-origin for each box that's generated and then apply the transform to each box separately. This means that something like: >>> >>> <span style="-moz-transform: rotate(45deg);">x<br>x</span> >>> >>> gets rendered with the two boxes offset from each other vertically by the line height and not offset horizontally and each rotated by 45 degrees clockwise. >> >> That's probably what we'd want to do in WebKit. It's a bit odd, especially with rotations, but I think it makes more sense than transforming all the boxes together (even though that would be easier for us to implement). > > It seems unexpected to me. I expect it to act more like position:relative. Can you explain why it makes more sense, and what use case would benefit by doing the child inlines separately? Position: relative only lets you offset the boxes horizontally or vertically, so I don't think it informs on this issue. What do you expect to happen when a split <span> has a rotation transform? Simon
Received on Tuesday, 31 August 2010 16:20:28 UTC