TimelinePanel: restore selectedRecord behevior by removing windowFilter.

BUG=
R=pfeldman@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@168885 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Revert 168880 "Make DOMWrapperWorld::current() callable from wor..."

A lot of tests are crashing at DOMWrapperWorld::isIsolatedWorld().
http://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux/builds/28365

> Make DOMWrapperWorld::current() callable from workers
> 
> This CL does the following two things:
> 
> - Makes DOMWrapperWorld::current() callable from workers. Now that a world is always stored in PerContextDataHolder::world(), DOMWrapperWorld::current() can just look up the PerContextDataHolder::world().
> 
> - Makes DOMWrapperWorld::current() callable even when a window object is being initialized. It's possible that some methods call DOMWrapperWorld::current() while the window is being initialized. To handles the subtle situation, this CL adds DOMWrapperWorld::worldOfInitializingWindow.
> 
> 
> BUG=341032
> NOTRY=true
> 
> Review URL: https://codereview.chromium.org/182903003

TBR=haraken@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@168886 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Wait for Close code in close-code-and-reason

Add a call to receive_message() to the handler in close-code-and-reason_wsh.py
to ensure it does not close the connection until it has received a response from
the client.

BUG=349901
TEST=close-code-and-reason.html layout test

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

git-svn-id: svn://svn.chromium.org/blink/trunk@168887 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Oilpan: Prepare to move DatabaseBackendBase and its subclasses to Oilpan heap, and add GC support to database threads.

This CL makes Database thread finalization synchronous by default in
order to avoid deadlock by ~WebThread, which wait until the thread gets
idle. We ask thread finalization in DatabaseContext::stop, which is called
in ExecutionContext::stopActiveDOMObjects, and the thread finalization
tasks are finished in it. Also, we don't need to close databases explicitly
in WorkerThread and FrameLoader.

Note:
* DatabaseBackendBase is ThreadSafeRefCounted, and we had no transition
types for it. This CL adds transition types for ThreadSafeRefCounted to Handle.h.
* Now PendingGCRunner can support any thread.
* Some Persistent handles for DatabaseBackendBase need to be
  CrossThreadPersistent because the owner object is created in the main or
 worker thread, and is destructed in the database thread.


BUG=347902

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

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