Remove excessive include of ActiveAnimations.h

CSSAnimations.h, having being changed 23 times in the last 90 days,
had prior to this patch roughly 507 targets depending on it. After
this patch, the number has shrunk to 17.

This patch removes unnecessary ActiveAnimation.h includes, from which
CSSAnimations.h is included.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@176748 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: [regression] screencast won't render element boxes in Inspect element mode

BUG=387552

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

git-svn-id: svn://svn.chromium.org/blink/trunk@176749 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Add functionality for editing and removing object properties of Symbol type.

BUG=376194

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

git-svn-id: svn://svn.chromium.org/blink/trunk@176750 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Bridge::destroy should wait for the completion of Peer::destroy

Bridge::initialize waits for the completion of Peer::initialize in order to avoid threading issues. Similarly, we should make Bridge::destroy wait for the completion of Peer::destroy to avoid threading issues. Specifically, the following threading issue can happen in oilpan builds:

(1) The worker thread calls Bridge::destroy.
(2) The worker thread finishes and calls a final GC to clean up the thread heap before Peer::destroy is triggered.

Then the final GC hits the empty ASSERT (which checks if the thread heap of the worker thread is empty) because the main thread still holds a reference to the SyncHelper, which is allocated on the thread heap of the worker thread. In order to make sure that the worker thread runs the final GC after the main thread clears the references to all objects allocated in the thread heap of the worker thread, we need to make the Bridge::destroy wait for the main thread to complete the Peer::destroy.

This issue doesn't happen in non-oilpan builds, so this CL adds the synchronization to oilpan builds only. (In any event, we cannot add the synchronization to non-oilpan builds, because Peer::destroy destructs the SyncHelper object and thus there is no way for the main thread to tell the worker thread that the main thread completes the Peer::destroy.)

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

git-svn-id: svn://svn.chromium.org/blink/trunk@176751 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: Make Page.getResourceContent async and do not perform it before InspectorResourceContentLoader is ready.

This is another step in preparation for preloading html documents content.

BUG=354447

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

git-svn-id: svn://svn.chromium.org/blink/trunk@176752 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Implement an infrastructure of Blink-in-JS (The IDL compiler part)

* A design doc is here: https://docs.google.com/a/google.com/document/d/13cT9Klgvt_ciAR3ONGvzKvw6fz9-f6E0FrqYFqfoc8Y/edit

* A full CL is here:
https://codereview.chromium.org/345893002/

* This CL implements the IDL compile part of the Blink-in-JS.

-- IDLExtendedAttributes.txt: Added a [PrivateScriptInterface] IDL extended attribute, which indicates that a given interface is an interface for Blink-in-JS.

-- v8_private_script_interface.py: A code generator for Blink-in-JS' IDL interface.

-- private_script_interface.{h,cpp}: Template files for Blink-in-JS' IDL interface.

-- TestPrivateScriptInterface.idl: Binding tests for a Blink-in-JS' interface.

-- DOMWrapperWorld.{h,cpp}: Added a new dedicated world for Blink-in-JS execution.

* This CL doesn't change any existing behavior, since Blink-in-JS is not yet used by any real code.

BUG=341031

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

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