- From: Håkon Wium Lie <howcome@opera.com>
- Date: Fri, 16 Aug 2013 04:02:44 +0200
- To: Brad Kemper <brad.kemper@gmail.com>
- Cc: Morten Stenshorne <mstensho@opera.com>, "robert\@ocallahan.org" <robert@ocallahan.org>, www-style <www-style@w3.org>
Brad Kemper wrote: > On Aug 15, 2013, at 2:39 AM, Morten Stenshorne <mstensho@opera.com> wrote: > > > "Robert O'Callahan" <robert@ocallahan.org> writes: > > > >> Microsoft introduced a large number of CSS properties controlling scrolling and > >> zooming in Windows 8: > >> http://msdn.microsoft.com/en-us/library/ie/hh920761%28v=vs.85%29.aspx > >> As far as I know, none of them other than touch-action have been proposed for > >> standardization so far. > >> > >> One of the features that we have use-cases for at Mozilla is the ability to > >> snap scrolling to land at specific offsets. One such use-case is touch-based > >> horizontal panning between pages of the home-screen in FirefoxOS. At the end of > >> the panning gesture the screen should show a single page, not parts of two > >> pages. An underlying physics model determines which page is selected when the > >> gesture ends, and the selected page snaps into place using animation. > > > > For such a use case, have you considered paged overflow [1][2]? > > That's exactly what I was thinking. There was an earlier thread where Håkon and I were discussing the paging effect, and having a property to set the effect. So, what you are suggesting might be as simple as this: > > Overflow:paged; > Page-transition: inline-push; /* new page pushes old page aside in the inline direction */ The simple switch was actually proposed by Robert way back: http://lists.w3.org/Archives/Public/www-style/2008Oct/0170.html -h&kon Håkon Wium Lie CTO °þe®ª howcome@opera.com http://people.opera.com/howcome
Received on Friday, 16 August 2013 02:03:25 UTC