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

Re: Thoughts on line grids and line spacing proposals

From: Ian Kilpatrick <ikilpatrick@google.com>
Date: Wed, 11 Oct 2017 11:23:12 -0700
Message-ID: <CAJL3UpSdEwp+mi8nTtOM9AzEbtm8Nvt19J-bJj5A61XFiES-dA@mail.gmail.com>
To: Florian Rivoal <florian@rivoal.net>
Cc: Alan Stearns <stearns@adobe.com>, "L. David Baron" <dbaron@dbaron.org>, "www-style@w3.org" <www-style@w3.org>
I filed a few issues, but there are a lot of subtle issues wrt. positioning
a non-BFC post-layout (and existing issues with how to position new-FCs but
that is a separate compat issue).

This is probably better as an in-person discussion, (it may also help to
talk about how blink is going to perform block-layout in the future, which
may clarify why some of these things are difficult - I'm happy to have a
break-out on this if there is interest and people would find it valuable).

On Mon, Oct 9, 2017 at 11:46 PM, Florian Rivoal <florian@rivoal.net> wrote:

> > On Oct 10, 2017, at 13:27, Alan Stearns <stearns@adobe.com> wrote:
> >
> > On 10/9/17, 8:15 PM, "Florian Rivoal" <florian@rivoal.net> wrote:
> > * The major issue I am seeing with this proposal is that it doesn't seem
> to do anything to address what was already the primary weakness of the
> existing line-grid proposal: snapping lines to the grid can change
> (increase) the size of their container, and in some layout modes, changing
> its size can change its position, which should imply a different snapping,
> and unless we explicitly break out of this one way or another, we've good
> an infinite loop.
> >
> > Please read https://drafts.csswg.org/css-line-grid/#alignment-
> interactions for a solution to this problem. One spacing adjustment to
> deal with size and position changes should be sufficient to break out of
> the loop. There are examples showing how this is done for centered and
> end-aligned content in the draft, but if you have other concerns I’m happy
> to work out additional examples to add.
> Hi Alan,
> You are right, I should have mentioned this existing proposal. As far as I
> can tell, the problem is the same in both variants of the line grid, so the
> solution should be the same. Workarounds like the keyword separation I
> suggested may be different, but the actual solution ought to be the same.
> As for this specific proposal, you have pointed me to in in the past, and
> I have not reported back with either satisfaction or issues. Apologies,
> that was very bad form.
> I do have issues with the solution outlined in that section of the
> line-grid. It does seem like a step in the direction of a solution, but I
> am not sure it is complete or well defined. Maybe I am just not
> understanding it fully, though. Anyway, whether it should be resolved or
> explained away, I have a issue about that, and this discussion can continue
> there. As it applies equally to the existing line-gird and to dbaron's
> proposal, here isn't the best place to discuss this. Sorry for not filing
> this issue a year (or more) ago.
> https://github.com/w3c/csswg-drafts/issues/1856
> —Florian

Received on Wednesday, 11 October 2017 18:23:38 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:15:05 UTC