Put generated parsetab.py in output directory.

The new Python parser generates a file, parsetab.py.
(This is expensive, so it is cached.)
The path defaults to the source directory, so it makes a mess in the user's
source files, and needs to be deleted.

This CL fixes this by putting it in the generated directory.

Longer-term, we should be able to generated this table as a build target,
and then run the parser in optimized mode, which should be faster,
but that's more involved (do later).

Review URL: https://chromiumcodereview.appspot.com/19576009

git-svn-id: svn://svn.chromium.org/blink/trunk@154746 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Throw exceptions on all failed cross-origin access checks.

Rather than special-casing access to Location properties[1], we should
allow developers to safely swallow cross-origin access check failures by
throwing an exception upon access to potentially interesting properties.

For example, Firefox currently throws exceptions for cross-origin access
such as `window.parent.NaN` and `window.parent.history`. This patch
matches that behavior by throwing on access to Window properties and the
History object.

[1]: http://src.chromium.org/viewvc/blink?view=rev&rev=154564

BUG=17325,237080
R=abarth@chromium.org

Review URL: https://chromiumcodereview.appspot.com/19932002

git-svn-id: svn://svn.chromium.org/blink/trunk@154747 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Revert 154720 "Node::lazyAttach should traverse into ShadowRoots"

> Node::lazyAttach should traverse into ShadowRoots
> 
> We never mark ShadowRoot as needing a lazyAttach so it doesn't have the right bits
> set and you can end up in situations where the ShadowRoot is never attached and
> distribution never runs.
> 
> I added a check to Document::recalcStyle that prints out any element that still
> needsStyleRecalc() at the end of the function and this change makes sure that
> all elements have their style recalculated at the end of recalcStyle.
> 
> This has proved hard to create a reduced test case for but we should add one eventually.
> Right now this change makes sense purely from a correctness standpoint even if it wasn't
> fixing the bug.
> 
> BUG=260509
> 
> Review URL: https://chromiumcodereview.appspot.com/19492008

TBR=esprehn@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@154748 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: Do not set distance to 0 for all objects held by global handles.

Only do so for Native Contexts that own user root objects.
The rest of objects should maintain their original distance from window.

R=yurys@chromium.org

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

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