You need at least 2 consecutive ticks to start a scroll.
Tested in Safari, Webkit nighties, Chrome, Firefox 3.3.6.
CPClipView -scrollToPoint: is never called.
It seems to me that the _DOMScrollingElement that handles native scrolling doesn't move.
Label: #new. What's next? A reviewer should examine this issue.
Milestone: Someday. Label: #new. What's next? A reviewer should examine this issue.
I can confirm that scrolling with one click doesn't do anything in the TableTests.
Milestone: Someday. Labels: #needs-review, AppKit, bug. What's next? This issue is pending an architectural or implementation design decision and should be discussed or voted on.
If the _DOMScrollingElement doesn't receive a native scrolling event, then there is nothing we can do. Can you check to see if that is the case? I don't have a mouse with a scroll wheel.
Milestone: Someday. Labels: #needs-info, #needs-review, AppKit, bug. What's next?
Line 1058 of CPPlatformWindow+DOM.j:
// We lag 1 event behind without this timeout.
That would explain why the first tick doesn't get noticed. @aljungberg will have to take care of this, he worked on this code.
Assignee: aljungberg. Milestone: Someday. Labels: #accepted, AppKit, bug. What's next? A reviewer should examine this issue.
I can confirm that this is still an issue (tested in lastest Chrome and Safari).
Sometimes up to 4 ticks are missed before scrolling starts.
interestingly on another maschine (chrome 36.0.1985.125, OSX10.9.4, logitech M90 scrollwheel), no tick is missed.
so it may be the mouse.
i don't see this anymore.
tested chrome, FF and safari (all latest)
Assignee: aljungberg. Milestone: Someday. Labels: #works-for-me, AppKit, bug. What's next? Attempts to reproduce the problem described by this issue have failed to reveal any erroneous situation.