Revert of [screen-orientation] Expose orientation info in OrientationInformation interface. (https://codereview.chromium.org/366853008/)

Reason for revert:
Speculative revert: seems like a cause of Linux_ASAN memory leak after blink roll.

http://build.chromium.org/p/chromium.memory/buildstatus?builder=Linux%20ASan%20LSan%20Tests%20%283%29&number=4884

Original issue's description:
> [screen-orientation] Expose orientation info in OrientationInformation interface.
> 
> BUG=162827
> 
> Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=177486

TBR=abarth@chromium.org,ch.dumez@samsung.com,mvanouwerkerk@chromium.org,sigbjornf@opera.com,mlamouri@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=162827

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177542 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Revert of Directly update composited transforms (https://codereview.chromium.org/365793005/)

Reason for revert:
Mac failures:

http://build.chromium.org/p/chromium.mac/buildstatus?builder=Mac%2010.6%20Tes...
http://build.chromium.org/p/chromium.mac/buildstatus?builder=Mac%2010.7%20Tes...
http://build.chromium.org/p/chromium.mac/buildstatus?builder=Mac%2010.7%20Tes...
and so on.

Original issue's description:
> Directly update composited transforms
> 
> This CL introduces a special case for updating composited transforms. Now when an
> element with an inline transform is composited, we can skip the bulk of the work
> in the compositing update and directly update the transform of its graphics layer.
> 
> To make this work, we need to skip the overlap test, which does work proportional
> to (the square of) the size of the document. We do this by assuming that later
> RenderLayers overlap layers that are composited and have inline transforms. Most
> of these layers will squash back down into a single graphics layer, so we won't
> cause a layer explosion.
> 
> In RenderLayer::styleChanged, we recognize the condition for a direct transform
> update and simply mark a single CompositedLayerMapping as needing a local graphics
> update. We could save more time by introducing a smaller GraphicsLayerUpdateScope
> just for transforms, but that's work for a future CL.
> 
> This CL makes the compositing update for the Polymer calculator ~9.1x faster. The
> entire time spent below WebViewImpl::layout is ~3.3x faster.
> 
> Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=177495

TBR=chrishtr@chromium.org,esprehn@chromium.org,vollick@chromium.org,abarth@chromium.org
NOTREECHECKS=true
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177543 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: Remove event filtering from tracing timeline event flamechart

We cannot do filtering at this point, as the flamechart items are built
basing on the recorded trace event levels. Thus if an event is filtered
out its children will hang in the air.

R=loislo@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@177544 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: Make TimelineFlameChart and data provider use proper TimelineUIUtils

R=loislo@chromium.org

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

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