Re: [css-break][css-overflow-3][css-regions][css4-ui] generalizing 'region-fragment' into a fragmentation primitive: a first step to solving multi-line ellipsis from Alan Stearns on 2015-03-11 (www-style@w3.org from March 2015)

From: Alan Stearns <stearns@adobe.com>
Date: Wed, 11 Mar 2015 17:23:41 +0000
To: Florian Rivoal <florian@rivoal.net>, www-style list <www-style@w3.org>
Message-ID: <969E89C7-C98C-4BA6-94CB-6C3F996C48AA@adobe.com>

On 3/10/15, 2:56 PM, "Florian Rivoal" <florian@rivoal.net> wrote:

>However, when working out what these various values compute to in 
>difference cases, I realized that ''next'' and ''auto'' end up meaning 
>the exact same thing in all cases (please check the spec for details). I 
>didn't think it made sense to have both, and picked ''next'' out of the 
>two so that the computed values would look better, but I was on the 
>fence, as ''auto'' is a better name for the initial value.

Could you go into your thinking here a bit more? I don’t understand why 
the computed values would look better with ''next'', and still prefer 
''auto'' for this value.

Thanks,

Alan

Received on Wednesday, 11 March 2015 17:24:10 UTC