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

Re: [css3-multicol] accessibility and UX

From: Shelby Moore <shelby@coolpage.com>
Date: Wed, 20 Oct 2010 17:26:38 -0400
Message-ID: <65047c63cf0df0ac6ae7d05542280790.squirrel@sm.webmail.pair.com>
To: shelby@coolpage.com
Cc: "Håkon Wium Lie" <howcome@opera.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, "Daniel Glazman" <daniel.glazman@disruptive-innovations.com>, "www-style@w3.org" <www-style@w3.org>
[snip]

>> I last raised the issue on this list here:
>>
>>   http://lists.w3.org/Archives/Public/www-style/2008Oct/0148.html
>>
>> The proposal has similarties with what (I believe) Shelby is proposing.
>
>
> Yes, but focus on Tab Atkin's modification, which makes it more like what
> I am proposing:
>
> http://lists.w3.org/Archives/Public/www-style/2008Oct/0196.html
>
>> The proposal was discussed at some length at the F2F meeting in
>> Mandelieu i October 2008:
>>
>>   http://www.w3.org/2008/10/20-css-irc.html
>>
>> The conclusion was that we should leave multicol as it is and add
>> something like "overflow-mode: paginate" in the future.
>
> What is the justification for allow cases that can forcing scrolling from
> bottom to top of document in order to read left-to-right?
>
> Shouldn't the default be to not to do that, then you can work on adding
> your other cases in the future?
>
> I can't understand punting on this one.  You are going to have a lot of
> angry people out there asking who made this decision?
>
>> I did that here:
>>
>>   http://lists.w3.org/Archives/Public/www-style/2009Jan/0030.html
>>
>> But it has since been removed. I'm happy to put it back on track.
>>
>> But the WG has decided, after discussions, to not address the issue in
>> the CSS3 multicol draft, which is now in CR.
>
> Who decided that?  Where can I read their logic?

I can guess on the 2nd question.  I suspect they couldn't decide what to
do because they are thinking in terms of breaking at the viewport edge,
but that is not what I (nor Tab Atkins?) was proposing.  I am saying that
by default when the user has nested a div to force vertical scrolling of
columns, at least break the column row on the multicol element edge.

You can later decide how you want to handle any paging options for columns
and the viewport.  That is an orthogonal issue.

Again I link back to the relevant explanation of the priority problem:

http://lists.w3.org/Archives/Public/www-style/2010Oct/0421.html
Received on Wednesday, 20 October 2010 21:27:05 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:33 GMT