[thelist] [css-d] The CSS Position Property

Barney Carroll barney.carroll at gmail.com
Thu Dec 16 02:09:16 CST 2010

Sorry, I think I'm using flow in a more abstract sense. Rather than source order, I mean positioning context. ie the determination of which other elements are interdependent on each-others' rendered position, and how they should react to each other.

Like position: relative (arbitrary positioning, but still within flow)? I can speculate on differences you might've been implying, like some kind of float: top/bottom. For me, that last extension would resolve a lot of issues I have with the conflict of arbitrary and inferred positioning.

The idea of putting a fixed element in flow is a tough one. The browser would need to re-render everything each time the page was scrolled, wouldn't it?

Sent from my iPod

On 16 Dec 2010, at 07:28, Chetan Crasta <chetancrasta at gmail.com> wrote:

> @Thierry: Happy to help.
>> the element is taken out of flow, thus float is rendered impotent
> @Barney: It doesn't necessarily follow that because the element is out
> of the flow, float cannot work. If the spec hadn't disallowed it, it
> would be conceivable for position:absolute and float to be used
> together to get the combined effect of 5) and 6), that is: a
> stretched, right or left aligned element, with text or inline elements
> flowing around it.
> http://roughtech.com/t/posit.html
> ~Chetan

More information about the thelist mailing list