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

Re: Positioned Layout proposal

From: Ojan Vafai <ojan@chromium.org>
Date: Mon, 18 Oct 2010 13:12:28 -0700
Message-ID: <AANLkTimPQwPE_e8a0DNu-UuLuhyB2hqk3zqdeqCwCAXO@mail.gmail.com>
To: Sylvain Galineau <sylvaing@microsoft.com>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, www-style list <www-style@w3.org>
On Mon, Oct 18, 2010 at 12:52 PM, Sylvain Galineau
<sylvaing@microsoft.com>wrote:

> > 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: www-style list
> > Subject: Positioned Layout proposal
> >
> > Since I've worked at Chrome, one of the things I've heard developers
> > complain about a lot is the weakness of absolute positioning.  For
> > example, our app devs commonly want to position tooltips relative to
> > arbitrary elements in a contenteditable area.
>
> More use-cases would be helpful.
>

One use-case that's addressed by this proposal is adding UI to rich-text
content. For example, adding resize corners to an image. The resize corners
should be tied to the location of the image, but not actually in the
contentEditable area (e.g. they shouldn't be deletable or show up in
innerHTML). As it is now, people use absolute positioning for this, but it's
both a lot of code and doesn't work that great (e.g. consider the issues
with scrolling).

Ojan
Received on Monday, 18 October 2010 20:13:21 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:32 GMT