Re: [css-figures][css-multicol][css-overflow] Ten CSS One-Liners to Replace Native Apps

On Jul 23, 2014, at 3:51 PM, Håkon Wium Lie <howcome@opera.com> wrote:

> I've written a piece on how CSS can reproduce functionality currently
> used in native apps. 
> 
>  http://alistapart.com/blog/post/ten-css-one-liners-to-replace-native-apps
> 
> The sample code is from CSS Figures and CSS Multicol, with a dash of
> CSS Overflow:
> 
>  http://figures.spec.whatwg.org/
>  http://www.w3.org/TR/css3-multicol/
>  http://dev.w3.org/csswg/css-overflow-3/#overflow-properties
> 

This reminded me of something I've been meaning to bring up regarding the overflow 
paged-* values. 

I think of 'paging' as the combination of two controls:
1. In what direction does content overflow? To the side? Up/down?
2. What is the unit of scrolling/overflow navigation? 1px? One viewport's dimension worth? 
One at a time of the author's set of image elements?

The overflow property seems a reasonable place to define the former; scroll snap points [1] 
are meant to specify the latter e.g. scroll-snap-points-x: repeat(100vw) scrolls one viewport
width at a time.

I *believe* this split is the direction we're headed but it's not 100% clear from current
specs (or your ALA article).

Another way to ask is, if the author specifies the following:

overflow: paged-x;
scroll-snap-points: repeat(50%);

Does it mean:

A) Fragment the content one container (viewport?) width at a time; but scroll one half container 
forward/backward.

....or does it mean:

B) overflow content shall go to the right (or left); prev/next page gestures move half a container worth

I'm assuming B but I can't tell from the current early stages of those drafts. 

These two things seem like they interact though. Interesting in hearing about how.

[1] http://dev.w3.org/csswg/css-snappoints/

Received on Thursday, 24 July 2014 00:56:45 UTC