On Sunday, 25 May 2014 14:57:13 UTC-7, Robert O'Callahan wrote: > On Mon, May 26, 2014 at 9:47 AM, Robert O'Callahan > <ro....@ocallahan.org>wrote: > > > > > On Sun, May 25, 2014 at 4:59 PM, L. David Baron <db....@dbaron.org> wrote: > > > > > >> On Saturday 2014-05-24 20:00 -0700, Jonas Sicking wrote: > > >> > I guess what I'm arguing is that smooth-scrolling vs. instant > >> > scrolling shouldn't be a per-element CSS property, but rather a > >> > per-callsite API argument. > >> > > >> I think I tend to agree; I noticed the same thing during the CSS WG > >> meeting last week and sent: > >> http://lists.w3.org/Archives/Public/www-style/2014May/0255.html > >> > >> > > I agree also. > > > > > > Actually non-auto values for the ScrollBehavior DOM API override the > scroll-behavior CSS property per spec. So I think the real question for us > is whether to implement the scroll-behavior property, or the ScrollBehavior > DOM API, or both. I think for now we should just implement the > ScrollBehavior DOM API. > > > > Rob >
Agreed. I have added a comment to the bug (Bug 1010538 / Comment 18) which reflects this: To address the feedback on dev-platform regarding the uncertainty of use cases for the scroll-behavior css property, the CSSOM scrolling API's can be implemented first as they appear to provide the most immediate value. If the updated scrolling API lands without the scroll-behavior css property, then a separate bug will be filed to track the scroll-behavior css property independently. Also, it is expected that the smooth scrolling will land in two stages. First will be an implementation based on APZ to solve our immediate use case (B2G home page) with a follow-up bug tracking an implementation independent of APZ. - Kip _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
