Simplify TONATIVE_*_EXCEPTIONSTATE* macros

By assuming that the |value| expression throws exceptions via the
ExceptionState object, and only via it, we can skip the v8::TryCatch
declaration and check. This is good since it is less code, and since
v8::TryCatch objects cost a bit of CPU time to initialize.

The correctness of this patch depends on
  https://codereview.chromium.org/559553003/
and
  https://codereview.chromium.org/556273003/
that make sure all type conversion helpers with an ExceptionState&
argument actually throw all exceptions via it.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@181796 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: extract TracingManager from TracingModel, step 2

This just moves code from sdk/TracingModel.js to timeline/TracingModel.js
and renames the former to sdk/TracingManager.js. No actual code was harmed.

BUG=412709

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

git-svn-id: svn://svn.chromium.org/blink/trunk@181797 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Revert of Revert of Mixed Content: Move subframe checks into ResourceFetcher. (patchset #1 id:1 of https://codereview.chromium.org/550083003/)

Reason for revert:
This wasn't the root cause of the non-V8 context call.

Original issue's description:
> Revert of Mixed Content: Move subframe checks into ResourceFetcher. (patchset #2 id:40001 of https://codereview.chromium.org/544573002/)
> 
> Reason for revert:
> calls V8 from a non-V8 context
> 
> Original issue's description:
> > Mixed Content: Move subframe checks into ResourceFetcher.
> > 
> > Currently we're checking for mixed content when loading the main
> > resource of subframes in two places: DocumentLoader and ResourceFetcher.
> > The former properly checks against the frame's parent frame, while the
> > latter bypasses the checks entirely by virtue of the request's
> > 'Resource::Type' being 'Main'.
> > 
> > This is both confusing and difficult to replicate when moving to the
> > brave new world of request contexts and frame types that Fetch now
> > defines.
> > 
> > This patch drops the DocumentLoader check, and moves the relevant
> > logic into ResourceFetcher::canRequest and
> > ResourceFetcher::checkInsecureContent.
> > 
> > BUG=400087
> > 
> > Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=181383
> 
> TBR=mkwst@chromium.org
> NOTREECHECKS=true
> NOTRY=true
> BUG=400087
> 
> Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=181543

TBR=jochen@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=400087

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

git-svn-id: svn://svn.chromium.org/blink/trunk@181798 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Don't clear StyleAffectedByEmpty before recalc.

ElementRareData::resetStyleState() cleared the StyleAffectedByEmpty flag
before recalculating style for an Element. However, this flag can be set by
style recalc for any of the sibling subtree elements in the presence of
adjacent combinators. If you have a LocalStyleChange for the element that
may become empty/non-empty, the flag can not be cleared since it may never
be set again unless the siblings affected by the :empty state are
recalculated.

R=esprehn@chromium.org
BUG=412950

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

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