I'd really like to see the CSS WG spend some time on properties that allowed more control over scrolling and zooming. Also something that addresses the complexity involved in building "long scrollable lists".
Right now a lot of websites implement their own scrolling behavior in JS by listening to UI events, cancelling their default behavior, and then setting various scroll related values through the DOM. UIs that snap scrolling to certain elements or that implement edge effects can't be done any other way. However this doesn't work well at all as we are moving to a world where scrolling happens off the main thread. Likewise, being able to implement a UI where a user can do zooming currently requires using JS to catch touch/mousewheel events, cancelling them, and then using the DOM to implement a zooming UI. UIs that allow zooming of a part of a webpage, for example zooming in on a picture or an email while leaving surrounding UI intact, can't be implementing right now without main-thread roundtrips. The touch-action CSS property defined in pointer-events attempts to address some of this, but falls far short. The obvious first problem is that it's touch specific (which is sort of ironic given that it's a spec that attempts to remove the separation between touch and mouse input). Finally there's the issue of how to use the DOM and CSS to create a lazily populated list. Currently lazily populating the DOM from a database leads to a lot of churn in reflows of content that's already on the page. These issues are *the* top difficulties on the layout side in creating a performant UI on low end mobile devices. I don't see any deliverables listed in the charter that's attempting to address this. Should we ask that it's added, or is it covered by any of the existing ones? / Jonas On Thu, May 8, 2014 at 5:22 PM, L. David Baron <dba...@dbaron.org> wrote: > The W3C is proposing a revised charter for: > > Cascading Style Sheets (CSS) Working Group > http://lists.w3.org/Archives/Public/public-new-work/2014May/0000.html > http://www.w3.org/Style/2013/css-charter.html > deadline for comments: May 29 > > Mozilla has the opportunity to send comments or objections through > May 29. Please reply to this thread if you think there's something > we should say. > > As with charters for other long-lived groups, the details in the > list of deliverables largely matter only in that they might > constrain what the group is allowed to work on without a new > charter; the dates tend to be largely fiction. > > My intent (unless I get other comments) is to support the charter, > but point to comments that have been made on the working group > mailing list since the charter was sent out for review (some of > which are about documents omitted from the list) so that the W3C has > a chance to incorporate those comments (which it probably wouldn't > if no AC representative mentioned them). > > -David > > -- > 𝄞 L. David Baron http://dbaron.org/ 𝄂 > 𝄢 Mozilla https://www.mozilla.org/ 𝄂 > Before I built a wall I'd ask to know > What I was walling in or walling out, > And to whom I was like to give offense. > - Robert Frost, Mending Wall (1914) > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
