Closed Bug 1247456 Opened 8 years ago Closed 8 years ago

Collect telemetry to measure how much jank various scroll input methods cause

Categories

(Core :: Panning and Zooming, defect, P5)

Product:
Core
Component:
Panning and Zooming
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
firefox47 --- wontfix
firefox48 --- wontfix
firefox49 --- wontfix

People

(Reporter: botond, Unassigned)

References

Details

(Keywords: feature, Whiteboard: gfx-noted) 

This is a follow-up to bug 1238137 to collect the amount of jank the various scroll input methods cause. Kats suggested this in bug 1238137 comment 5.
I wouldn't spend too much time on this if it ends up being nontrivial. I don't know if it'll end up being worth the effort.
Whiteboard: gfx-noted,feature
Keywords: feature
Whiteboard: gfx-noted,feature → gfx-noted
I'd be ok with WONTFIX'ing this bug entirely. Not really worth the effort IMO.
status-firefox47: affected → wontfix
status-firefox48: --- → affected
Priority: -- → P5
(In reply to Kartikaya Gupta (email:kats@mozilla.com) from comment #2)
> I'd be ok with WONTFIX'ing this bug entirely. Not really worth the effort
> IMO.

So then, what's the priority for the different input methods getting APZ?
To me mouswheel scrolling is secondary to autoscrolling. I highly doubt scrollbars and their buttons are frequently used. I guess touch is inportant because mobile.
(In reply to avada from comment #3)
> So then, what's the priority for the different input methods getting APZ?
> To me mouswheel scrolling is secondary to autoscrolling. I highly doubt
> scrollbars and their buttons are frequently used. I guess touch is inportant
> because mobile.

The telemetry added in bug 1238137 is showing that the three very heavily used input methods that are not already going through APZ are keyboard up/down arrows, scrollbar dragging, and autoscrolling. I imagine we will make an effort to support each of these in APZ (scrollbar dragging already has an experimental implementation behind the "apz.drag.enabled" pref).
Oh, there's also touch event support which is already implemented, but enabling it by default is blocked on bug 1170342 for Linux and bug 1244402 on Windows (there are no Mac touchscreens AFAIK). On mobile it has been enabled since the beginning of APZ.
Bumping out of 48. Botond, I'll let you make the call on whether or not to wontfix the bug entirely. I'm in favor of wontfix'ing.
status-firefox48: affected → wontfix
status-firefox49: --- → affected
It would be interesting to have this data, but it's probably not worth the engineering effort at this time.

I'm going to WONTFIX this for now. We can revisit that decision if necessary.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.