Delete FrameLoader::m_policyDocumentLoader.

This is a second attempt at
http://src.chromium.org/viewvc/blink?view=revision&revision=148729

BUG=none
TEST=none

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

git-svn-id: svn://svn.chromium.org/blink/trunk@150289 bbb929c8-8fbe-4397-9dbb-9b2b20218538
[TestResultServer] Make getParsedExpectations method report errors.

- Make the method strict by complementing error handling code.
- Take tokens with bug PREFIXES as bug entries. Current code parses path tokens with a substring "Bug" as bug entries.
- Add unittests.

BUG=240294

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

git-svn-id: svn://svn.chromium.org/blink/trunk@150290 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: [Network] Negative time displayed in "Connecting" info row.

DNS Lookup time is considered to be a part of connecting time.

This is incorrect since:
https://src.chromium.org/viewvc/chrome?revision=175412&view=revision

BUG=236649
R=vsevik@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@150291 bbb929c8-8fbe-4397-9dbb-9b2b20218538
DevTools: [Resources] Renaming '' (empty string) storage item doesn't work properly.

There were no way to distinguish empty key and no-key (for new items.
Now editing node initially has null values for all columns.
So renaming is distinguishable from creation of new item.

BUG=224227

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

git-svn-id: svn://svn.chromium.org/blink/trunk@150292 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Make Event.path() return a pre-calculated NodeList rather than calculating it dynamically.

The current implementation of Event.path() populates a NodeList dynamically when Event.path() is called.
That has a drawback: If an event handler mutates a DOM tree, the returned value of event.path() will be changed.

This patch pre-calculates a NodeList for each node so that event.path() should not be affected by mutating DOM tree.

BUG=240162

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

git-svn-id: svn://svn.chromium.org/blink/trunk@150293 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Rewrite time complexity tests

For review; needs testing on bots before committing, else will be flaky.

3 major changes, 3 minor changes:
* Rewrites testing (LayoutTests/resources/magnitude.js)
* Sets parameters on individual tests
* Fix test expectations:
  9 tests were marked as flakey, replaced with 1 slow and 3 failures
Also:
* tweak one test so uses a random number for better accuracy
* workaround to make 1 test not Slow
* 1 minor test HTML fix (make valid HTML 5)

Patch is large b/c of rewriting testing almost completely,
and updating all the tests for the new framework.
(If helpful, could break up by turning off all tests instead,
then individually turning them on.)

For testing, diff isn’t v. useful b/c substantially a rewrite;
a portion of code is retained though.
For individual tests and expectations, the diffs are useful:
for individual tests this shows the parameters (and minor changes),
while for test expectations it shows the bottom line.

For magnitude.js (main file), it's 500 lines, of which 1/4 are comments,
mostly explaining the stats and parameters.

It's structured as:
* main loop (Magnitude.run, Magnitude._runTime),
* utility functions,
* auxiliary computations (mostly Magnitude._OLS for ordinary least squares),
* statistical tests:
  Magnitude._isConstant
  Magnitude._isLogarithmic
  Magnitude._isLinear
  Magnitude._isPolynomial

The basic structure (run test repeatedly, time by measuring iterations in
a given time) is unchanged, but the details of measuring and the tests
themselves have changed substantially.

In the stats sections there are a lot of variables, so that the stages of
computations are clear, so the functions are long but not dense.
The actual test is always just "max deviance <= tolerance".

The meat is in the computations; the actual logic is pretty straightforward,
with the hairiest functions being:
* Magnitude._isLogarithmic
  ...as the log testing is statistically trickier
  (iterative least squares, throwing out extreme points)
* Magnitude._runTime
  ...b/c of various tricks to reduce measurement error,
  notably averaging and retries

Beyond review, needs testing on try bots, else likely will fail,
as parameters have only been tested on my workstation and may be
too strict on bots.

Please feel free to get other opinions and suggest other reviewers!

R=ojan@chromium.org
BUG=232244

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

git-svn-id: svn://svn.chromium.org/blink/trunk@150294 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Added CodeGeneratorV8 support for String return type in
named getter IDL methods.

Generated code originally assumed return types were
RefCounted.

BUG=238174

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

git-svn-id: svn://svn.chromium.org/blink/trunk@150295 bbb929c8-8fbe-4397-9dbb-9b2b20218538
During deletion, we make style and link elements to direct child of editable root in DeleteSelectionCommand::makeStylingElementsDirectChildrenOfEditableRootToPreventStyleLoss().

Although, if style and link elements don't have root editable element, e.g. inside contentnEditable="false", appendNode() refers null pointer.

This patch changes to avoid above situation.

BUG=177470
R=ojan@chromium.org

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

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