Final step to remove wallClockTime API from animation delegate interface.

We are currently removing trying to remove all references to base::Time (wall
clock time) from Chrome/Blink compositor/graphics stack.

This requires multiple two-sided patches. Following the process found at
https://groups.google.com/a/chromium.org/d/msg/chromium-dev/ukaRczAK6t8/0ludyZ1Nu4cJ

The steps are;
 * Adding monotonic only API to Blink's animation delegate interface
   https://codereview.chromium.org/185633002

 * Making the delegate adapter use monotonic only API
   https://codereview.chromium.org/185643002

 * (This Patch) -- Remove the wallClockTime API from Blink/WebKit.
   https://codereview.chromium.org/185393005

BUG=299945

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

git-svn-id: svn://svn.chromium.org/blink/trunk@168889 bbb929c8-8fbe-4397-9dbb-9b2b20218538
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

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=168880

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

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

I mis-committed this CL without passing try bots.
I'll revert it and reland it through a commit queue.

> 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
> 
> Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=168880
> 
> Review URL: https://codereview.chromium.org/182903003

TBR=haraken@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@168891 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Show reason when preview or response tab is empty on network tab of inspector

BUG=130294

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

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