W3C home > Mailing lists > Public > www-style@w3.org > November 2012

Re: [css-regions] Concern about CSS regions flowing into generated content

From: Elliott Sprehn <esprehn@gmail.com>
Date: Sun, 11 Nov 2012 13:07:04 -0800
Message-ID: <CAPJYB1gk_-go2SA7Dxz9psrCuCAAfPGP14aBe=JYVk=+Qn+XZQ@mail.gmail.com>
To: Andrei Bucur <abucur@adobe.com>
Cc: Alan Stearns <stearns@adobe.com>, www-style list <www-style@w3.org>
On Wed, Oct 10, 2012 at 5:05 AM, Andrei Bucur <abucur@adobe.com> wrote:

> ...

> From a specification standpoint, the behaviour for pseudo-elements is
> currently defined like this:
> "If the ‘content’ property computes to something else than ‘normal’ (or
> ‘none’ for a pseudo-element), the block container does not become a CSS
> Region. If the ‘content’ property computes to ‘normal’ (or ‘none’ for a
> pseudo-element), then the block container becomes a CSS Region and is
> ordered in a region chain according to its document order."
> This definition basically allows a pseudo-element to become a region only
> if the content property evaluates to "none". This way the content property
> will always have priority and the pseudo-element's box will be used to flow
> content if nothing else is specified.
What you describe seems reasonable, but it still bothers me that the
primitive for putting things like form controls into ::before and ::after
is Regions and we offer no simpler and saner alternative in the platform. :)

I think Mozilla has proposed an alternative to the current design of
regions that side steps all this that I like a bit better.

Regarding the WebKit implementation, do you think that closing
> https://bugs.webkit.org/show_bug.cgi?id=95117 will also solve the
> fragility concerns of the pseudo-elements in WebKit? If not, is there
> something you think I can help you with?

Getting that landed should solve a lot of the fragility in WebKit, yes.

- E
Received on Sunday, 11 November 2012 21:09:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:23 UTC