Make applyMultiplier retain RenderStyle ptrs only during layout.

This should be a functional nop but slightly reduce memory impact of
resetMultipliers.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@173457 bbb929c8-8fbe-4397-9dbb-9b2b20218538
HTMLAnchorElement.text should not be readonly

HTMLAnchorElement.text should not be readonly as per the HTML specification:
http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#dom-a-text

On setting HTMLAnchorElement.text, we must act as if the textContent IDL
attribute on the element had been set to the new value. This CL updates Blink
to behave accordingly.

The new behavior is consistent with Firefox 29 and IE11.

R=arv@chromium.org, eseidel@chromium.org
TEST=fast/dom/HTMLAnchorElement/set-text.html
BUG=369950

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

git-svn-id: svn://svn.chromium.org/blink/trunk@173458 bbb929c8-8fbe-4397-9dbb-9b2b20218538
HTMLTableSectionElement.insertRow(0) / HTMLTableRowElement.insertCell(0) do not behave correctly

HTMLTableSectionElement.insertRow(0) / HTMLTableRowElement.insertCell(0) do not
behave correctly according to the HTML specification:
http://www.whatwg.org/specs/web-apps/current-work/multipage/tabular-data.html#dom-tbody-insertrow
http://www.whatwg.org/specs/web-apps/current-work/multipage/tabular-data.html#dom-tr-insertcell

Previously, Chromium was adding the new element before the first node, instead
of before the first <tr> (for insertRow) or <td> / <th> (for insertCell)
element.

The new behavior also matches the behavior of Firefox 29.

R=arv@chromium.org, tkent@chromium.org
BUG=369803
TEST=fast/dom/HTMLTableSectionElement/insertRow-skips-non-tr.html
TEST=fast/dom/HTMLTableRowElement/insertCell-skips-non-td-th.html

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

git-svn-id: svn://svn.chromium.org/blink/trunk@173459 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Fix interaction between --fully-parallel and --run-singly in run-webkit-tests.

By default, with --fully-parallel each test is run in its own shard in
run-webkit-tests, and so a given content_shell may run tests from different
directories in succession; this is normally fine, but when flipping back and
forth between virtual tests and normal tests, you might have to restart
content_shell to change the command line arguments, making things run much
more slowly. So, we keep all of the tests in a virtual suite together
even with --fully-parallel.

*However*, if you're running with --run-singly (or --batch-size=1), like
we do on the valgrind bots, then you are restarting between each test anyway.
Further, we're likely only running a small number of tests at a time,
it's possible that we'd end up with a single shard to run, and not be able
to exploit multiple processes.

This patch changes the logic so that we will also shard every virtual test
if --run-singly is true.

R=ojan@chromium.org
BUG=369325

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

git-svn-id: svn://svn.chromium.org/blink/trunk@173460 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Auto-rebaseline for r173442

http://src.chromium.org/viewvc/blink?view=revision&revision=173442

BUG=361729
TBR=enne@chromium.org

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

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