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

Re: [css3-regions] content:flow-from() vs. flow-from

From: Brad Kemper <brad.kemper@gmail.com>
Date: Thu, 11 Aug 2011 09:16:55 -0700
Cc: Alex Mogilevsky <alexmog@microsoft.com>, Øyvind Stenhaug <oyvinds@opera.com>, "www-style@w3.org" <www-style@w3.org>
Message-Id: <4FFA4043-D4A4-47D1-9ACF-D70D2224E99E@gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>

On Aug 11, 2011, at 8:43 AM, Tab Atkins Jr. wrote:

> On Thu, Aug 11, 2011 at 6:47 AM, Alex Mogilevsky <alexmog@microsoft.com> wrote:
>> As for "position:relative", in this hypothetical situation (of defining display and positioning properties as if they didn't exist yet) I would keep it separate, as it isn't really specifying a position, it is an offset from a position that is determined before it applies.
>> 
>> Perhaps something like this would work better for relative positioning:
>> 
>>        position-offset: <length> <length>?
>> 
>> (the two values are offsets for 'start' and 'before'; somewhat similar to http://www.w3.org/TR/css3-gcpm/#the-float-offset-property)
> 
> I agree with François - position:relative was a way to do a
> purely-visual translation of an element before transforms existed.
> Now that they do exist, if we were doing it over again, we'd just use
> transform.

Does 'translateZ' change an element's z-index? Does '‘transform-style: preserve-3d’ affect that? I couldn't really tell by reading the spec. Or are you saying that with 'translateZ' we wouldn't need z-index or need relative positioning to set it?
Received on Thursday, 11 August 2011 16:18:03 GMT

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