Merge GraphicsLayer and GraphicsLayerChromium - part 1

The merge is split into stages to reduce risk of making errors. This part moves
only data members, and necessary includes/declarations to support those data
members. Next parts will merge actual logic and eventually remove GraphicsLayerChromium.

BUG=238016

Review URL: https://chromiumcodereview.appspot.com/14736009

git-svn-id: svn://svn.chromium.org/blink/trunk@149802 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Rename RenderLayer::scrollOffset() to adjustedScrollOffset()

RenderLayer::scrollOffset() is used to return m_scrollOffset + scrollOrigin().
This behavior is very confusing and error-prone.

No test needed. There is no behavioral change.

R=jamesr@chromium.org

Review URL: https://chromiumcodereview.appspot.com/14865006

git-svn-id: svn://svn.chromium.org/blink/trunk@149803 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Require use of
AudioBus::create() to avoid ref-counting issues

BUG=235733

Review URL: https://chromiumcodereview.appspot.com/14628008

git-svn-id: svn://svn.chromium.org/blink/trunk@149804 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove captureEvents and releaseEvents

These two are Netscape 4 specific and are currently implemented as no ops.

They are not part of any standard and IE9+ managed to get by without
implementing stubs for them.

BUG=238243

Review URL: https://chromiumcodereview.appspot.com/14929004

git-svn-id: svn://svn.chromium.org/blink/trunk@149805 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Disable inspector/timeline/timeline-load.html due to crash

BUG=238363
TBR=aarya@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@149806 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Respect enable bool in enableStableFeatures now that the dust has settled.

BUG=237740

Review URL: https://chromiumcodereview.appspot.com/15019003

git-svn-id: svn://svn.chromium.org/blink/trunk@149807 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Continue cleaning up garden-o-matic unit test failures.

There's still so much work to do. We really ought to run these on a
waterfall or something.

R=ojan
BUG=

Review URL: https://chromiumcodereview.appspot.com/14674010

git-svn-id: svn://svn.chromium.org/blink/trunk@149808 bbb929c8-8fbe-4397-9dbb-9b2b20218538
[CSS Exclusions] ExclusionShape bounding box methods should return LayoutRects

Redefined the ExclusionShape API in terms of LayoutUnits, instead of floats: all of the ExclusionShape methods now have LayoutUnit parameters and return LayoutUnit values. This is more natural, since the callers work exclusively in LayoutUnits. This is strictly a refactoring, no new tests were needed.

The impetus for this change was some feedback from Levi and Julien about an earlier change - https://codereview.chromium.org/14289003/.

The LayoutUnit to float conversions have always occured at the boundary between the layout system and the ExclusionShape classes. Previously these conversions were mostly implicit and ad-hoc, and the callers found them somewhat confusing. Refactoring the ExclusionShape API in terms of LayoutUnits simplifies life for the callers and ensures that the conversions are systematic.

BUG=235085

Review URL: https://chromiumcodereview.appspot.com/14892005

git-svn-id: svn://svn.chromium.org/blink/trunk@149809 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Make DocumentFragment constructable

http://dom.spec.whatwg.org/#documentfragment

This allows us to do `new DocumentFragment` instead of
`document.createDocumentFragment()`.

BUG=238232

Review URL: https://chromiumcodereview.appspot.com/14940005

git-svn-id: svn://svn.chromium.org/blink/trunk@149810 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Beat down remaining garden-o-matic unit test failures.

There was a bit of flakiness introduced by adding two types
of ways to retrieve the builder info and results. Removing that
code fixed it.

R=ojan@chromium.org
BUG=

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

git-svn-id: svn://svn.chromium.org/blink/trunk@149811 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Waste less memory in TreeShared in DEBUG builds.

Yes, we don't care about memory in Debug builds, but we do run them on
the bots, and this takes 4 bytes out of a Node on 32 bit platforms.

BUG=

Review URL: https://chromiumcodereview.appspot.com/14576004

git-svn-id: svn://svn.chromium.org/blink/trunk@149812 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Sort WebRuntimeFeatures.h in preparation for autogeneration

BUG=237740
R=abarth@chromium.org

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

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