DevTools: Accept executionContextId in WorkerRuntimeAgent.cpp

BUG=

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172525 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove RuntimeEnabledFeatures.h includes from a few headers

Changing RuntimeEnabledFeatures.in requires many files to be recompiled.
Getting rid of these unnecessary includes didn't help much, but still...

BUG=none

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172527 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove linux_use_tcmalloc and switch to use_allocator in Blink.

See https://src.chromium.org/viewvc/blink?revision=168591&view=revision,
the bug and http://crrev.com/255129 for the details.

BUG=345554

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172528 bbb929c8-8fbe-4397-9dbb-9b2b20218538
CompositedLayerMapping::updateInternalHierarchy crashes with squashing

Before this CL, CompositedLayerMapping::updateScrollingLayers
could call updateInternalHierarchy, but that's inconsistent
with the general approach of these functions, which is to
return a bool indicating whether the internal hierarchy has
changed. When updateScrollingLayers was called in the
CompositedLayerMapping destructor, we would update the
internal hierarchy while it was in an inconsistent state,
causing a crash.

In this CL, I've removed the call to updateInternalHierarchy
in updateScrollingLayers to prevent this inconsistent update.
Instead, I've taught the one caller of updateScrollingLayers
how to do the extra work that updateScrollingLayers requires
when it changes layers.

BUG=366281

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172529 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Floats Don't Overhang Their Block Formatting Context
Per http://www.w3.org/TR/CSS2/visuren.html#float-position: "References
to [the elements] in the [rules that govern the behaviour of floats]
refer only to other elements in the same block formatting context
as the float."

This means we don't need to look for intruding or overhanging floats
in boxes that establish a new block formatting context. I couldn't
find a test where we failed this rule but we do appear to be doing
unnecessary work in rebuildFloatsFromIntruding() so make sure we
avoid adding floats from different block formatting contexts.

The next step here is to merge the appropriate parts of avoidFloats()
and createsBlockFormattingContext() as they are frequently synonymous.

BUG=

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

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