Revert of Selectively disable rubber banding on mac (part 2). (https://codereview.chromium.org/219473003/)

Reason for revert:
This CL causes regressions in vertical content scrolling.

https://code.google.com/p/chromium/issues/detail?id=365034

Original issue's description:
> Selectively disable rubber banding on mac (part 2).
> 
> The logic for handling 2-finger swipes should be:
> 1. If a 2-finger swipe can scroll the content (or iframe), it should do so.
> 2. If the 2-finger swipe can cause history navigation, it should do so.
> 3. The 2-finger swipe should rubber-band the content view.
> 
> (2) is handled by the embedder, and (1 & 3) by the renderer. Right now, the
> renderer is passed an IPC, and it tries to do (1), and then it tries to do (3).
> I've modified the event passed in so that there are flags that prevent the
> renderer from performing (3) under specific circumstances.
> 
> There was an existing mechanism to determine whether the renderer should try
> (3), but it was fragile, incorrectly used, and insufficient for newer features
> in chrome - the user can cancel a history swipe without cancelling the gesture,
> at which point rubber-banding should be possible again. I've simplified and
> fixed the logic inside ScrollElasticityController.mm to reflect the desired
> behavior.
> 
> This is part 2 of a two-part change. It includes the changes to
> ScrollElasticityController to use the new parameters on the WheelEvent. It also
> removes references to the old 2 parameter constructor for platformWheelEvent,
> in favor of the 4 parameter constructor.
> 
> BUG=321437
> 
> Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=170989

TBR=asvitkine@chromium.org,thakis@chromium.org
BUG=321437

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172429 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Auto-rebaseline for r172408

http://src.chromium.org/viewvc/blink?view=revision&revision=172408

BUG=361729
TBR=enne@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172430 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Create ResourceTimingInfo in willStartLoadingResource()

FontResource defers calling FontResource::load() until the resource
is actually needed. This makes ResourceTimingInfo's initial time
inaccurate. This CL is a workaround which waits to create ResourceTimingInfo until ResourceFetcher::willStartLoadingResource() is called.

BUG=323750

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172432 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Set proper referrer for css resource fetching

Fetching css resources are initiated as follows:
  - Create FetchRequest
  - Call ResourceFetcher::fetchXXX()

git-grep shows me that CSSImageValue, CSSImageSetValue and
CSSFontFaceSrcValue are all of the resource fetch initiators
which live in css/. I think that setting referrer in these
classes should cover all css resource fetching.

Since resource fetching is delayed until the resource is actually
needed, we need to hold the referrer somewhere.
This CL modifies the css parser to set referrer to corresponding
CSSValue (CSSImageValue and CSSFontFaceSrcValue) when it sees url(...).

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172433 bbb929c8-8fbe-4397-9dbb-9b2b20218538
[webcrypto] Add key usage for 'deriveBits'

BUG=245025

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172434 bbb929c8-8fbe-4397-9dbb-9b2b20218538
use shifts to speedup floor() and round()

BUG=

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172435 bbb929c8-8fbe-4397-9dbb-9b2b20218538