- From: Rick Byers <rbyers@chromium.org>
- Date: Mon, 22 Sep 2014 19:34:56 -0400
- To: Timothy Dresser <tdresser@google.com>
- Cc: Simon Pieters <simonp@opera.com>, "www-dom@w3.org" <www-dom@w3.org>, Nathaniel Duca <nduca@chromium.org>
- Message-ID: <CAFUtAY-AsNHrmoutcRNWx_eSPHk7WmbKDgRYtS6e+eS-35ht8A@mail.gmail.com>
Note that we're also discussing this over in www-style: http://lists.w3.org/Archives/Public/www-style/2014Sep/0297.html. It may make more sense in CSSWG, especially if we add a CSS knob for explicitly opting into synchronized scrolling. Note that Nat Duca recently gave a great talk describing how we've come to this view, why we're reasonably optimistic about 60fps apps that run JS (and even repaint) every frame: https://www.youtube.com/watch?v=3Bq521dIjCM. Also coupled into this whole debate is that we need an API to make it possible to build cross-browser smoothness benchmarks, so the community can more easily compare jankiness between browsers (and take us to task when we don't live up to our promise here). This is being discussed on public-web-perf: http://lists.w3.org/Archives/Public/public-web-perf/2014Sep/0040.html. I'm concerned that this difference in technical opinion is becoming an increasing impediment to advancing the web in fundamental yet interoperable ways (on both sides of the debate). I'd love to brainstorm about how we might unblock the stalemate here. Is there any interest in having a discussion around this at TPAC perhaps? Rick On Fri, Sep 19, 2014 at 9:03 AM, Timothy Dresser <tdresser@google.com> wrote: > Sorry, to be clear, I have no idea which spec this belongs in. > Let us know what you think is best. > > We assumed the event definition belonged in the DOM (or UI) event specs, > as that's where the scroll event is defined. > > Thanks, > Tim Dresser > > On Fri, Sep 19, 2014 at 8:23 AM, Timothy Dresser <tdresser@google.com> > wrote: > >> The scroll event is defined in the DOM events spec here: >> http://www.w3.org/TR/DOM-Level-3-Events/#event-type-scroll >> >> We will likely want to add to CSSOM View as well as the DOM events spec, >> to clarify some of the details on scrolling behavior. >> >> Tim Dresser >> >> On Fri, Sep 19, 2014 at 8:05 AM, Simon Pieters <simonp@opera.com> wrote: >> >>> On Thu, 18 Sep 2014 19:00:01 +0200, Timothy Dresser < >>> tdresser@chromium.org> wrote: >>> >>> Hi, >>>> >>>> In order to implement UI effects which customize or respond to >>>> scrolling, >>>> some developers currently resort to re-implementing scrolling >>>> <http://cubiq.org/iscroll-5>. This is bad for three reasons: >>>> >>>> ... >>>> >>> >>> If we add something for this it seems like it should go into CSSOM View, >>> since that currently defines the 'scroll' event. I've filed >>> https://www.w3.org/Bugs/Public/show_bug.cgi?id=26854 >>> >>> -- >>> Simon Pieters >>> Opera Software >>> >> >> >
Received on Monday, 22 September 2014 23:35:45 UTC