W3C home > Mailing lists > Public > www-style@w3.org > October 2012

Re: [css3-transforms] Mapping 3D rendering context to document

From: Dirk Schulze <dschulze@adobe.com>
Date: Thu, 18 Oct 2012 21:37:21 -0700
To: Rik Cabanier <cabanier@gmail.com>
CC: "www-style@w3.org list" <www-style@w3.org>
Message-ID: <A2993729-9D7D-4D73-8DBD-47EAAD8BFFE8@adobe.com>


On Oct 18, 2012, at 9:17 PM, "Rik Cabanier" <cabanier@gmail.com<mailto:cabanier@gmail.com>> wrote:

I read the bug report but didn't really understand what your question is.
Could you rephrase?

The question is if we there is a need to specify how a 3D rendering context gets drawn into the coordinate system of the ancestor element. Or if the current specification text is sufficient enough. This needs the input of implementers.

Greetings
Dirk


reading your report:

One understanding problem that I had on reading the section about creating a 3D rendering context is the following sentence: "An element that establishes a 3D rendering context also participates in that context." What does it mean for the local coordinate space of the root element of the rendering context?

Doesn't every element establish its own matrix with respect to CSS transforms?

Rik

On Thu, Oct 18, 2012 at 5:20 PM, Dirk Schulze <dschulze@adobe.com<mailto:dschulze@adobe.com>> wrote:
> Hi,
>
> We have a bug report on how to map a 3D rendering context into a 2D document. It would be great to get input from browser vendors if any input on the CSS3 Transforms is needed and if so, how it should look like[1].
>
> Greetings,
> Dirk
>
> [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=17433


Received on Friday, 19 October 2012 04:37:49 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:01 GMT