Revert of Do not scan the active part of the stack in oilpan conservative garbage collections. (https://codereview.chromium.org/152513006/)

Reason for revert:
Caused http/tests/workers/terminate-during-sync-operation.html to crash. 

http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%40ToT%20Blink&tests=http%2Ftests%2Fworkers%2Fterminate-during-sync-operation.html


Original issue's description:
> Do not scan the active part of the stack in oilpan conservative garbage collections.
> 
> If threads are allowed to continue after safepointing there is a
> stack marker. We should stop stack scanning at the marker in that
> case. If there is no marker the thread whose thread we are iterating
> will be blocked and we should scan all the way to the recorded
> end stack pointer.
> 
> R=vegorov@chromium.org
> BUG=
> 
> Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=166634

TBR=vegorov@chromium.org,haraken@chromium.org,wibling@chromium.org,ager@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=

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

git-svn-id: svn://svn.chromium.org/blink/trunk@166720 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Oilpan: Add HeapCollection thread affinity detection traits.

While investigating Keishi's changelist I noticed that these
were missing. They determine the thread affinity for heap
allocated collections. This is needed in order to get
persistent handles to such collections allocated in the
right thread heap.

R=haraken@chromium.org, vegorov@chromium.org
BUG=

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

git-svn-id: svn://svn.chromium.org/blink/trunk@166723 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Make the event *related-target* resolution algorithm work for multiple shadow trees.

The relevant spec issue is: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24351

This is similar to https://codereview.chromium.org/145533002,
where I've made the event retargeting algorithm work for multiple shadow trees.

On the other hand, this patch fixes the *related-target* resolution algorithm for multiple shadow trees.

There has been an issue in *related-target resolution algorithm* for multiple shadow trees.
If a target is in the younger shadow tree and a related-target is in the older shadow tree, an event listener in the older shadow tree could see the node in the younger shadow tree as a related target. That should be fixed.

This patch correctly implements the relevant spec and fixed the issue.

I've also added assertions for non-nullness of adjusted targets (and adjusted related-targets) by early checking target's document and related target's document.

BUG=337089

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

git-svn-id: svn://svn.chromium.org/blink/trunk@166724 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: Migrate anchor click-revelation to extensions

R=pfeldman

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

git-svn-id: svn://svn.chromium.org/blink/trunk@166725 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Add an assertion to make sure that event.path used in user shadow trees doesn't leak nodes in user-agent shadow trees.
This assertion should always pass because insertion points in user shadow trees can't select nodes from user-agent shadow trees.

TEST=No behavior change
BUG=None

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

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