Merge 158542 "Fix sample time calculation in CPU profiler"

> Fix sample time calculation in CPU profiler
> 
> Convert hit count to the time in ms when the CPU profile is loaded and use only time after that, not hit count. Before this change there was a mix of hit count with sample time in different parts of code.
> 
> BUG=None
> R=alph@chromium.org
> 
> Review URL: https://codereview.chromium.org/25269003

TBR=yurys@chromium.org

Review URL: https://codereview.chromium.org/25843002

git-svn-id: svn://svn.chromium.org/blink/branches/chromium/1650@158779 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Merge 158284 "[Mac] Fix rubberband overhang appearing after a co..."

> [Mac] Fix rubberband overhang appearing after a content size change.
> 
> This was caused by r152374, which changed the wheel phase end event to
> not always call snapRubberBand(). Which resulted in some state persisting
> even after the scroll, such as m_inScrollGesture being true, causing issues
> later.
> 
> For example, it would cause ScrollView::updateScrollbars() to later believe
> rubber banding was in progress and not reset the scroll position on a
> content size change (leading to this bug).
> 
> This CL changes the code to always call snapRubberBand() on a phase end
> event, like before r152374.
> 
> Additionally, it makes snapRubberBand() to not start a timer to revert the
> state if there's no overhang or momentum scroll, which removes a race (i.e.
> a resize before the timer fires) and makes the test more straight forward.
> 
> BUG=290590
> TEST=See bug.
> 
> Review URL: https://chromiumcodereview.appspot.com/24284003

TBR=asvitkine@chromium.org

Review URL: https://codereview.chromium.org/25917002

git-svn-id: svn://svn.chromium.org/blink/branches/chromium/1650@158832 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Merge 158576 "Fix rubber-band overhang getting stuck after a fling."

> Fix rubber-band overhang getting stuck after a fling.
> 
> This got broken by: https://chromiumcodereview.appspot.com/24284003
> 
> That CL made the code not start the timer under certain cases
> when PlatformWheelEventPhaseEnded was received.
> 
> This caused a problem with momentum scroll. How that works is
> after the regular scroll events are received, including the
> PlatformWheelEventPhaseEnded event, then momentum scroll
> events start appearing.
> 
> The momentum events can then cause overscroll when a fling
> happens. However, the cleanup after that was expected to
> happen in the snapRubberBand timer launched from the phase
> end event (which now wouldn't be getting launched).
> 
> This CL fixes the issue by starting the snap rubber band
> timer when a momentum scroll starts (if it hasn't been
> started during the phase end event).
> 
> BUG=290590
> 
> Review URL: https://codereview.chromium.org/24486006

TBR=asvitkine@chromium.org

Review URL: https://codereview.chromium.org/25886003

git-svn-id: svn://svn.chromium.org/blink/branches/chromium/1650@158834 bbb929c8-8fbe-4397-9dbb-9b2b20218538