- From: Alex Mogilevsky <alexmog@microsoft.com>
- Date: Mon, 18 Oct 2010 20:23:00 +0000
- To: Tab Atkins Jr. <jackalmage@gmail.com>, www-style list <www-style@w3.org>
> -----Original Message----- > From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf Of Tab Atkins Jr. > Sent: Monday, October 18, 2010 12:32 PM > > To fix this, I've written a personal draft of a new Positioned Layout spec > I'd like to see adopted by the group. It's currently hosted on my blog: > <http://www.xanthir.com/blog/b48H0>. It is certainly interesting. Need to look closer to understand the implications... Some questions: 1) I wonder if the most important use cases (yes, we need more use cases) can be solved by just specifying a positioning parent? 2) It appears easy when it only applies to absolute positioning (although implementation will not be that easy - it will complicate calculating visual bounds, incremental update, pagination and more...). But will it be enough? If such a major concept is added to layout model, wouldn't it be expected to extend to in-flow content (which of course would be much harder, adding circular size dependencies)? Alex
Received on Monday, 18 October 2010 20:23:45 UTC