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

RE: Positioned Layout proposal

From: Sylvain Galineau <sylvaing@microsoft.com>
Date: Mon, 18 Oct 2010 21:25:06 +0000
To: Ojan Vafai <ojan@chromium.org>
CC: Tab Atkins Jr. <jackalmage@gmail.com>, www-style list <www-style@w3.org>
Message-ID: <045A765940533D4CA4933A4A7E32597E280AD6E1@TK5EX14MBXC115.redmond.corp.microsoft.com>
Allowing for overlays scenarios such as resize icons definitely sounds like an interesting use-case for this. Thanks !

From: ojan@google.com [mailto:ojan@google.com] On Behalf Of Ojan Vafai
Sent: Monday, October 18, 2010 1:12 PM
To: Sylvain Galineau
Cc: Tab Atkins Jr.; www-style list
Subject: Re: Positioned Layout proposal

On Mon, Oct 18, 2010 at 12:52 PM, Sylvain Galineau <sylvaing@microsoft.com<mailto:sylvaing@microsoft.com>> wrote:
> From: www-style-request@w3.org<mailto:www-style-request@w3.org> [mailto: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 21:25:40 GMT

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