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

Re: Positioned Layout proposal

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 18 Oct 2010 14:54:27 -0700
Message-ID: <AANLkTikL5wuW24OCK6aAVguDLbwabLBt5fGQ=JKc3yo1@mail.gmail.com>
To: Sylvain Galineau <sylvaing@microsoft.com>
Cc: www-style list <www-style@w3.org>
On Mon, Oct 18, 2010 at 2:44 PM, Sylvain Galineau
<sylvaing@microsoft.com> wrote:
> CSS terminology is not what I'm asking for.
> Your draft spec already tells me what the
> feature does in CSS terms.
> What design scenario is solved by this particular
> construct ? What is the author trying to achieve on
> the page for the user's benefit ? I could describe
> how adjoining floats can be merged in CSS terms; that
> doesn't tell anyone what scenario it's useful for.
> Your email below describes *how* some use-case is
> resolved by your proposal in CSS terms without
> defining what the actual use-case is.
> Positioning tooltips is a use-case. Ojan's scenario
> to allow the positioning of resizing icons over an
> image is a use-case. Freezing table headers is a use-case.
> These are really helpful in framing the proposal and judging
> its value.
> "Abspos a child above, below, or to the side of its parent"
> is not. Sorry...

I described a use-case in more detail in the email you quote.  I want
to show extra information on hover without moving the rest of the page
around (possibly overlapping other elements).

Another would be placing annotations in the margins alongside some
text - google docs does this.

Received on Monday, 18 October 2010 21:55:22 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:39 UTC