New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 595691 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Feature



Sign in to add a comment

Smooth Scrolling API for extensions

Reported by jari.pen...@gmail.com, Mar 17 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36

Steps to reproduce the problem:
Smooth scrolling is a good feature, but it needs to be more adjustable. I suggest smooth scrolling API for extensions which would allow safe alternatives to smooth scrolling extensions that currently work by mangling the JavaScript on all pages.

What is the expected behavior?

What went wrong?
Problem is the current smooth scrolling is not very adjustable, and the extensions which allowes customization works by injecting JS to all pages, which is horribly unsafe (and error prone) approach for it.

E.g. for my taste the keyboard scrolling is now nearly unusable because the step is way too small. Mouse wheel scroll feels too fast or too stepped.

Did this work before? No 

Chrome version: 49.0.2623.87  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 21.0 r0
 
Cc: rnimmagadda@chromium.org
Labels: Needs-Feedback
@jari.pennanen: Could you please provide us the Steps to reproduce, Expected & Actual Results along with a sample file, this would help us in triaging it further.

Also, please provide us the screen-recording for better understanding.

Thank you.
@rnimmagadda huh? This is not a bug report, a feature request: Smooth Scrolling API for extensions. The smooth scrolling works as expected but is not configurable by extensions.

I'm saying in above a general statement: Smooth Scrolling requires fine tuned settings so extensions like: 

https://chrome.google.com/webstore/detail/smoothscroll/nbokbjkabcmbfdlbddjidfmibcpneigj

https://chrome.google.com/webstore/detail/chromium-wheel-smooth-scr/khpcanbeojalbkpgpmjpdkjnkfcgfkhb

Wouldn't have to inject JavaScript on all pages to implement smooth scrolling with poor results compared to native smooth scrolling.
Project Member

Comment 3 by sheriffbot@chromium.org, Mar 19 2016

Labels: -Needs-Feedback Needs-Review
Owner: rnimmagadda@chromium.org
Status: Assigned (was: Unconfirmed)
Thank you for providing more feedback. Assigning to requester "rnimmagadda@chromium.org" for another review.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
Components: Platform>Extensions>API
Labels: -Type-Bug -Needs-Review Type-Feature
Owner: ----
Status: Untriaged (was: Assigned)
Could someone from Dev team please look into this feature request.

Thank you.
Cc: lazyboy@chromium.org skobes@chromium.org
Components: Blink>Input
cc: input-dev, skobes for smooth scroll related question.

Comment 6 by skobes@chromium.org, May 20 2016

Owner: rbyers@chromium.org
I don't think we should do this, adding customization hooks to the smooth scrolling implementation would introduce significant complexity to benefit a small subset of users.

But I'll let input-dev make the final decision here.
Cc: ymalik@chromium.org rbyers@chromium.org
Owner: tdres...@chromium.org
Status: Assigned (was: Untriaged)
tdresser@ can you comment on the scroll customization?
Status: WontFix (was: Assigned)
Customizable smooth scroll is relatively unrelated to scroll customization, if I understand correctly.

What's being asked for here is a way to modify the way smooth scroll behaves. This potentially could be done through scroll customization, but I don't think we should make that an explicit goal, and I don't think we should add customization knobs for smooth scroll either.

If there's enough demand to change how smooth scroll behaves that it would be worth adding this capability, it probably means we should change how smooth scroll behaves for everyone.

As per #6, marking WontFix.
Labels: Hotlist-Input-Dev

Sign in to add a comment