Open Bug 964097 Opened 6 years ago Updated 19 days ago

[meta] Implement CSSOM-View smooth scrolling spec

Categories

(Core :: DOM: CSS Object Model, enhancement, P2)

enhancement

Tracking

()

People

(Reporter: fb+mozdev, Unassigned)

References

(Blocks 1 open bug, )

Details

(Keywords: dev-doc-needed, meta)

CSSOM-View defines a new property for scroll{,To,By,IntoView}() to indicate a "native" smooth scrolling in pages. :bz already voiced support for this property on the www-style mailing list: http://lists.w3.org/Archives/Public/www-style/2013Mar/0314.html

There's also a new scroll-behaviour CSS property that may be moved to a different spec. That property should probably be implemented in a follow up bug.
Severity: normal → enhancement
See Also: → 331031
Blocks: 1004779
No longer blocks: 1004779
Duplicate of this bug: 1004779
Bug 1010538 has been added for the implementation of the scroll-behavior css property.
feature-b2g: --- → -
No longer blocks: vertical-homescreen
feature-b2g: - → 2.1
Hey Jet, Milan - I'm not sure whos team would most likely take this feature up, but I was wondering if we could have this in 2.1.

In order to have smooth scrolling performance in the vertical homescreen during dragdrop and return-to-top operations, this is extremely important. Currently we use javascript to manually scroll the page, and it looks really janky. Please let me know if you need any more information from myself. Thanks!
Flags: needinfo?(milan)
Flags: needinfo?(bugs)
Kip Gilbert is working on this in bug 1010538. Please add your requests/requirements to that bug.
Flags: needinfo?(bugs)
Flags: needinfo?(milan)
Morphing this into a meta bug. I think the feature-b2g should no longer apply here (since it's a meta bug) but to any dependant bug. But you make the call. I don't know if the flag applies to DOM changes or the CSS property (covered by Bug 1010538) either.
Depends on: 1010538
See Also: 1010538
Summary: Implement CSSOM-View smooth scrolling spec. → [meta] Implement CSSOM-View smooth scrolling spec
Note: As far as I can see, there is no bug for the DOM changes yet so if you want to set the tracking flag for those, please file a new one blocking this bug. Thanks!
See Also: → 945584
Blocks: 1033468
QA Whiteboard: [2.1-feature-qa+]
QA Whiteboard: [2.1-feature-qa+] → [2.1-feature-qa-]
QA Whiteboard: [2.1-feature-qa-] → [2.1-feature-qa?]
QA Whiteboard: [2.1-feature-qa?]
Whiteboard: [2.1-feature-qa+]
Flags: in-moztrap?(npark)
QA Contact: npark
Hi kip, I was looking for some examples that uses the new smooth-scrolling spec to QA test it, and milan told me you're the person to speak to.  Could you point me to the right direction?  Thanks!
Flags: needinfo?(kgilbert)
Got information from kip offline
Flags: needinfo?(kgilbert)
moztrap test case link:
https://moztrap.mozilla.org/manage/case/14507/
Flags: in-moztrap?(npark) → in-moztrap+
Gregor, some questions: 
1. do you think we can still land this to 2.1? 
2. who could be the best one to own this meta bug? 
Thank you!
Flags: needinfo?(anygregor)
Probably too late for 2.1 now. :jet should be a good driver here.
feature-b2g: 2.1 → 2.2?
Flags: needinfo?(anygregor)
As of last week, Kip was confident this will land in time for 2.1 - this week.  So, let's leave it to Kip and Jet to change this flag, if needed.  Now, Gregor may be commenting on nobody from Gaia actually taking advantage of this functionality in 2.1 - I don't have an argument with that.
feature-b2g: 2.2? → 2.1
Flags: needinfo?(kgilbert)
(In reply to Milan Sreckovic [:milan] from comment #12)
> As of last week, Kip was confident this will land in time for 2.1 - this
> week.  So, let's leave it to Kip and Jet to change this flag, if needed. 
> Now, Gregor may be commenting on nobody from Gaia actually taking advantage
> of this functionality in 2.1 - I don't have an argument with that.

Partial support of the specification has already landed with Bug 1022818 and Bug 1026023.  This includes the DOM methods that will most benefit GAIA features such as home screen scroll nudging.  In order to be useful in creating smoother scrolling on B2G, Bug 1022825 will also need to land.

Bug 1022825 is currently in review and can be landed as soon as I get a review+.
Flags: needinfo?(kgilbert)
QA Whiteboard: [2.1-feature-slip+]
My understanding based on the drivers discussion on this was cut from 2.1. If so, we should remove the feature-b2g 2.1 flag here.

Milan - Can you confirm?
Flags: needinfo?(milan)
feature-b2g: 2.1 → 2.2?
Flags: needinfo?(milan)
QA Whiteboard: [2.1-feature-slip+]
Whiteboard: [2.1-feature-qa+]
I think "native" smooth scrolling would be a nice topic for a blog post on Mozilla Hacks. :Kip, maybe you can team up with Robert (editor of HMO) if you agree? I wouldn't publish it before the pref ("layout.css.scroll-behavior.enabled" if anybody is interested in trying it out) is flipped by default and/or propagates to Aurora, though.
Flags: needinfo?(robert)
Flags: needinfo?(kgilbert)
Absolutely, sounds very interesting! :Kip, feel free to e-mail me at robert@mozilla.com and we can talk more!
Flags: needinfo?(robert)
(In reply to Robert Nyman from comment #16)
> Absolutely, sounds very interesting! :Kip, feel free to e-mail me at
> robert@mozilla.com and we can talk more!

I would love to help put together something for Mozilla Hacks once the dust settles in the next couple of weeks.  I've touched base with Robert by email.
Flags: needinfo?(kgilbert)
No longer blocks: 1033468
No longer blocks: 1087559
Depends on: 1087559
Sheila, can you follow up this topic or find someone to see what the next plan is? Thanks.
feature-b2g: 2.2? → ---
Flags: needinfo?(smooney)
Kevin, as far as I know, this is still in Fx 36. I will verify for sure but I may not be able to get confirmation until after the holiday break. I will try though.
Flags: needinfo?(smooney)
Based on the information I got from Sheila, all required/requested items are done. 
Thank you, Sheila.
Blocks: cssom-view-1
Priority: -- → P2

How can users with visual motion sensitivities block this implementation? Smooth scrolling in general can be a migraine trigger. An easier-to-block implementation would be an improvement over the current nightmare.

(In reply to MarjaE from comment #23)

How can users with visual motion sensitivities block this implementation? Smooth scrolling in general can be a migraine trigger. An easier-to-block implementation would be an improvement over the current nightmare.

Could you file a bug and needinfo? me on it? Should be straight-forward to ignore and always do non-smooth scrolling whenever prefers-reduced-motion evaluates to true.

You need to log in before you can comment on or make changes to this bug.