W3C home > Mailing lists > Public > www-style@w3.org > March 2015

Re: [css-overflow] fragments vs paginate

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 18 Mar 2015 19:13:01 -0700
Message-ID: <CAAWBYDARcMfXYmK_UMkMocC5OkR4jTThQN39NBryhaGrJJEYfA@mail.gmail.com>
To: Brad Kemper <brad.kemper@gmail.com>
Cc: www-style list <www-style@w3.org>, Florian Rivoal <florian@rivoal.net>
On Wed, Mar 18, 2015 at 6:21 PM, Brad Kemper <brad.kemper@gmail.com> wrote:
>> On Mar 18, 2015, at 2:02 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
>> I don't know if we really need a separate property for this.  It's not
>> an independent concern; it only applies when you're fragmenting.  We
>> could probably just (later) allow an <integer> argument after the
>> "paginate" keyword, so you'd write "continue: paginate 2;" rather than
>> "continue: fragments; n-up: 2;".
> Hmm. Maybe, but that seems odd to me. The '2' would only apply if it was paginate, so it's mere presence would indicate that that your fragments required a control to see them all (which is mainly how paginate differs from fragment). So, I don't know how it would be better than 'continue: fragments 2;'.

"fragments 2" doesn't indicate "this stuff is paginated", while
"paginate 2" does.  And "paginate" is definitely better than
"fragments 1".

It also feels better to reserve the "fragments" syntax space for any
future fragments-related options we might need, rather than
immediately merging it with the "paginate" case.

> And if it's only advantage over 'continue: fragments; n-up: 2;' is saving some space, it doesn't seem worth it. Having a separate property seems more clear, and allows that property to be set independently.

If two things aren't realistically useful to cascade separately,
there's not much reason to make them separate properties.  If you want
an easy switch between 1 and 2 pages, you just do "continue:
paginate;" vs "continue: paginate 2;"; using "continue:paginate;" and
"n-up: 2;" doesn't help you any.

We can always add subproperties in the future, of course, if
pagination gets another knob to twiddle or something.  That would make
it more useful to be able to cascade the bits independently.  Right
now, though, the "number of pages" is the sole control in the
pagination mode, so it doesn't add any new abilities to make it a
separate property.

Received on Thursday, 19 March 2015 02:13:48 UTC

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