Re: CSS Regions considered harmful (was: [css-regions] issue 16858 redux)


I contacted the Firefox list or IRC a while back and asked for advice on
 how to implement something like the fragment-overflow
specification. The answer was that this isn't
possible, because the fragment spec requires all the fragments to be
siblings of oneanother. This seems to significantly limit the use cases of
fragment-overflow. If you should decide to go for the fragment-overflow
specification instead, I would strongly recommend that you extend it to at
least cover all the current use cases of CSS Regions.

On Thu, Jan 23, 2014 at 7:24 AM, L. David Baron <> wrote:

> On Wednesday 2014-01-22 14:30 -0500, Brian Kardell wrote:
> > Is there a plausible alternative to #1 with any kind of serious
> > thought/support?  This is an entirely serious question, I'm sure it
> sounds
> > snarky or accusatory or something - but it is entirely genuine.  I
> respect
> > and actually agree with your goals, I just honestly cannot any longer
> > imagine a solution and I've not seen one which I think doesn't merely
> trade
> > a set of fairly well known problems for which we have, for all it's
> > problems, learned to use pretty effectively for an unknown set which we
> > can't say those things about (i.e., will people grok/adopt/etc - and then
> > what are the holes we come across as it spreads out).
> I've been trying to develop one at
> although I
> haven't had much time to work on it lately.
> -David
> --
> π„ž   L. David Baron                  𝄂
> 𝄒   Mozilla                   𝄂
>              Before I built a wall I'd ask to know
>              What I was walling in or walling out,
>              And to whom I was like to give offense.
>                - Robert Frost, Mending Wall (1914)

Johannes Wilm
Fidus Writer

Received on Thursday, 23 January 2014 11:59:09 UTC