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

Re: Inline elements should be affected by 2D Transforms

From: Brian Blakely <anewpage.media@gmail.com>
Date: Thu, 2 Jun 2011 13:26:02 -0400
Message-ID: <BANLkTim1CnKOX_rRFBD8AbnKEgFMSeoKTg@mail.gmail.com>
To: www-style@w3.org
Note: there was a typo in the original inline vs. inline-block example; it's
fixed now.

http://jsfiddle.net/brianblakely/fZ2uw/

<http://jsfiddle.net/brianblakely/fZ2uw/>-Brian


On Thu, Jun 2, 2011 at 12:41 AM, Brian Blakely <anewpage.media@gmail.com>wrote:

> *Point 1:*
> Three major browsers (Firefox, IE, Opera) already behave as desired.  Only
> Webkit "complies" by not rendering transforms on inline elements.
>
> *Point 2:*
> There are definitive instances where *inline-block* (often used as a
> workaround for Chrome/Safari to enable 2D Transforms on inline elements) is
> either insufficient or inelegant, instances served very well by *display:
> inline;*
> *
> *
> See fiddle output:
> http://jsfiddle.net/brianblakely/fZ2uw/
>
> Every character in the body is wrapped with a *span*.  These elements are
> inline by default.  Checking the box in the output will render them as
> inline-blocks.
>
> The result is a non-formatted text flow.  Aside from the lack of space
> characters, word breaks are no longer in effect.
>
> *Addendum:*
> *
> Webkit bug and the associated comment trail:
> https://bugs.webkit.org/show_bug.cgi?id=58965
>
>
> -Brian
> *
>
Received on Thursday, 2 June 2011 17:26:49 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:41 GMT