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

Re: [css-writing-modes-3] Defer auto-muticol behavior in Auto-sizing Block Containers in Orthogonal Flows

From: Koji Ishii <kojiishi@gmail.com>
Date: Sat, 30 May 2015 01:47:04 +0900
Message-ID: <CAN9ydbUZ74Y_UOb4m=ULfz33bFtexiURsON_CJ1O5kn1LfGAoA@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: W3C www-style mailing list <www-style@w3.org>
By the way, allow me to do one clarification, as I may still
misunderstand something.

On Fri, May 29, 2015 at 7:46 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> The only reason for "auto-multicol" is to handle the case of "infinite
> inline-axis space" in a way that's not super user-hostile.  The naive
> behavior *is* extremely user-hostile; it effectively makes the
> orthogonal element max-content in the inline axis (requiring the user
> to scroll back and forth to read lines of text; we all know how
> terrible this is when reading some accidentally-long <pre> text) and,
> if there's enough block-axis content, overflowing in the page's
> secondary scrolling direction (the one that's annoying to scroll in).
> That situation never occurs anywhere except orthogonal flows, because
> the inline axis space is always finite when all the writing modes
> match.

I'm all good for UA to handle "infinite inline-axis space". I agree we should.

What I'm suggesting here is for UA not to handle the overflow in block
direction automatically and forcibly.

Was this point clear?

Received on Friday, 29 May 2015 16:47:31 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:51 UTC