- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 18 May 2011 23:47:03 -0700
- To: fantasai <fantasai.lists@inkedblade.net>
- Cc: Alex Mogilevsky <alexmog@microsoft.com>, "www-style@w3.org" <www-style@w3.org>
On Wed, May 18, 2011 at 5:04 PM, fantasai <fantasai.lists@inkedblade.net> wrote: > On 05/18/2011 04:55 PM, Alex Mogilevsky wrote: >> >> ą -----Original Message----- >> ą From: www-style-request@w3.org [mailto:www-style-request@w3.org] On >> Behalf >> ą Of fantasai >> ą Sent: Wednesday, May 18, 2011 4:43 PM >> ą >> ą I would like to see GCPM's float-related features become a >> ą CSS3 Floats module. I don't have much of an opinion yet on what the >> ą features should look like or whether they should incorporate any >> ą additional functionality or how they should integrate with other >> floating >> ą proposals, but GCPM floats (and CSS2 floats and clearance) by themselves >> ą seem like enough material to make a coherent module. >> >> Do you also think it should be a separate CSS3 positioning >> (by that I mean not just Tab's proposal but also all of CSS2)? > > If there's a module that extends CSS2's positioning model (rather > than creating a new one), it should include the definitions for > CSS2's positioning model. This gives the opportunity to clean up > prose, make things more understandable, spec out areas that are > undefined, and ensure that the new model's integration is > well-defined with the old. > > However, if the new "Positioning" module is largely orthogonal > to CSS2 abspos, then such an approach to scoping the module won't > make as much sense. :) I'm intending to extend CSS2's positioning model, not create a new one. ~TJ
Received on Thursday, 19 May 2011 06:47:50 UTC