15755 2012-01-27 20:17:49 +0000 Inline boxes should be transformable too 2012-01-30 20:51:18 +0000 1 1 1 Unclassified CSS Transforms unspecified All All RESOLVED WONTFIX P2 normal --- 1 ayg smfr cmarrin dbaron dino dschulze eoconnor oldest_to_newest 63209 0 ayg 2012-01-27 20:17:49 +0000 """ transformable element A transformable element can either be a block-level or atomic inline-level element, not splitted into multiple inline-level boxes, from the HTML namespace, or an element which has the attributes ‘transform’, ‘patternTransform’ or ‘gradientTransform’ in the SVG namespace (see [SVG11]). """ http://dev.w3.org/csswg/css3-transforms/#TermTransformableElement Test-case: data:text/html,<!doctype html> <div style=width:100px> The quick brown fox jumped over the lazy dog </div> In IE9, Firefox 12.0a1, and Opera Next 12.00 alpha, the transform works fine. In Chrome 17 dev, the transform doesn't work. I suggest the restriction be lifted, so any element can be transformed. 63216 1 smfr 2012-01-28 07:58:36 +0000 This was discussed at some length at a F2F meeting. The issue with transforming line boxes is how to treat split boxes. There is no good answer that matches author expectation. 63341 2 ayg 2012-01-30 16:51:22 +0000 Can you give an example where it's not clear what browsers should do? Why isn't it enough to say that everything is laid out as it normally would be, then transforms are applied to whatever parts of line boxes are transformed? This is how relative positioning works for inline elements, no? 63344 3 smfr 2012-01-30 18:33:30 +0000 Consider Here is some text. Do you rotate the two line boxes as one, or rotate them individually? What's the transform-origin? 63346 4 ayg 2012-01-30 19:05:39 +0000 Ah, I see. Good catch. Browsers are indeed not interoperable here. For instance, if you try this: Suddenly everything turned upside-down! IE and Opera mangle it badly, and only Gecko gets the intended effect. On the other hand, if you do Suddenly everything turned upside-down! then it works roughly as intended in all browsers. So I have no problem with saying transforms have no effect on non-replaced inline elements. If we have good use-cases and someone comes up with a definition that works, we could define behavior at that point. 63356 5 smfr 2012-01-30 20:51:18 +0000 Sounds good.