W3C home > Mailing lists > Public > www-style@w3.org > February 2014

Re: [css-line-grid] Are named grids required?

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 26 Feb 2014 14:06:48 -0800
Message-ID: <CAAWBYDDT1EHHijaJyVnochbLx63H38Rdk7g+UiX74hKMZZf80Q@mail.gmail.com>
To: Alan Stearns <stearns@adobe.com>
Cc: fantasai <fantasai.lists@inkedblade.net>, www-style list <www-style@w3.org>
On Wed, Feb 26, 2014 at 2:01 PM, Alan Stearns <stearns@adobe.com> wrote:
> On 2/26/14, 1:55 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:
>
>>On Wed, Feb 26, 2014 at 1:31 PM, Alan Stearns <stearns@adobe.com> wrote:
>>> On 2/26/14, 1:21 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:
>>>>I like "match-parent", but is it useful to allow something to opt out
>>>>of the line-grid without establishing a new one?  (That is, an
>>>>explicit "none" value?)
>>>
>>> My thought has been that line-grid only determines whether an element
>>> establishes a new line grid or inherits the existing grid from a parent.
>>> It’s the line-snap (and box-snap or block-snap?) properties that allow
>>>for
>>> opting in or out of using the grid for positioning boxes.
>>>
>>> So while the initial value of line-grid needs to allow for using a
>>> pre-existing grid, I’m not sure there’s a use for turning off the grid
>>> from this property.
>>
>>Ah, right.  In that case, no need for more values.  I like fantasai's
>>"match-parent", then.  I think I prefer "new" over "create".
>
> I am ashamed to submit so quickly to the lure of bikeshedding, but what
> about continue|start?

match-parent has precedent, and I think better communicates what it
does - use the same grid as your parent.

~TJ
Received on Wednesday, 26 February 2014 22:07:35 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:19 UTC