Closed
Bug 1190990
Opened 10 years ago
Closed 7 years ago
Scrolling too sensitive on touch screen on Aha website
Categories
(Web Compatibility :: Site Reports, defect, P5)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: krudnitski, Unassigned)
References
()
Details
(Whiteboard: [needscontact])
If I'm here: https://mozilla.aha.io/products/FENN/feature_cards and I touch the screen to scroll down, it is too sensitive and jumps WAY below my target. I have to use my mouse to drag the scroll bar down.
Comment 1•10 years ago
|
||
I can reproduce this as well, and I think it's a bug in the "wheel" handler on "project-board-scroller" div on the page. It doesn't happen if you scroll the page using the parking lot div on the right side. Do you know who owns the Aha website?
| Reporter | ||
Comment 2•10 years ago
|
||
I'm sure we could find out given we hold an account with them.
Updated•10 years ago
|
Component: Panning and Zooming → Desktop
Product: Core → Tech Evangelism
Comment 3•10 years ago
|
||
Oddly enough, when I try to scroll *with* a wheel on desktop the behaviour seems to be the opposite: scrolling is unusually slow.. Why do they feel it's appropriate or required to interfere with the scrolling?
Whiteboard: [needscontact]
Comment 4•10 years ago
|
||
For the record blassey also reported a very jittery scrolling experience on Aha, using the trackpad on OS X.
Comment 5•9 years ago
|
||
I just tried to log in to see if this is still an issue and got the following message:
"Your account has been cancelled"
I'm guessing Mozilla isn't using this tool anymore? Brad, do you know?
Flags: needinfo?(blassey.bugs)
Comment 6•9 years ago
|
||
I think we we considering transitioning off it. Someone from the product team would know better. Barbara?
Flags: needinfo?(blassey.bugs) → needinfo?(bbermes)
Comment 9•7 years ago
|
||
Resolved as Fixed.
Status: NEW → RESOLVED
Closed: 7 years ago
Priority: P3 → P5
Resolution: --- → FIXED
| Assignee | ||
Updated•7 years ago
|
Product: Tech Evangelism → Web Compatibility
You need to log in
before you can comment on or make changes to this bug.
Description
•