Auto-rebaseline for 153949

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

BUG=169377
TBR=hclam@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@153961 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Revert 153959 "Style resolution: Apply animation properties earlier in a separate pass"

> Style resolution: Apply animation properties earlier in a separate pass
>
> In order to apply the results of animations earlier in the style cascade
> we need to apply animation related properties, generate animations and
> trigger transitions earlier in the process.
>
> This change introduces a new pass in the style application process which
> allows animation properties to be applied after variable definitions but
> before high priority and low priority properties.
>
> Evaluated performance using html5-full-render perf test on Nexus 7 and
> observed no regression.
>
> Covered by existing tests. No change in behavior.
>
> NOTRY=true
> BUG=232273
>
> Review URL: https://chromiumcodereview.appspot.com/18686005
>

Broke the windows build

TBR=dstockwell@chromium.org
BUG=232273
NOTRY=true

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

git-svn-id: svn://svn.chromium.org/blink/trunk@153962 bbb929c8-8fbe-4397-9dbb-9b2b20218538
ENABLE_8BIT_TEXTRUN=1 on Windows

Every other platform understands 8 bit text runs. Windows should join the club.

This CL contains a call to make16BitFrom8BitSource, which means we're doing a
memcpy when shaping 8 bit text runs in the complex text path. That's consistent
with how the other platforms handle this case.

R=eae@chromium.org
BUG=254708

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

git-svn-id: svn://svn.chromium.org/blink/trunk@153963 bbb929c8-8fbe-4397-9dbb-9b2b20218538
ContentSecurityPolicy shouldn't use bloatedCharacters

This CL removes all the calls to bloatedCharacters in ContentSecurityPolicy.
Rather than templating all this parsing code, I've used a temporary
Vector<UChar> to hold the UChars during parsing. That means we have an extra
memcpy or two, but this code isn't performance sensitive.

R=eseidel
BUG=254708

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

git-svn-id: svn://svn.chromium.org/blink/trunk@153964 bbb929c8-8fbe-4397-9dbb-9b2b20218538
HarfBuzzShaper shouldn't use bloatedCharacters

There's no reason to call bloatedCharacters on this line. The string is always
already 16 bits wide.

R=pdr
BUG=254708

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

git-svn-id: svn://svn.chromium.org/blink/trunk@153965 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove unused ENABLE_XHR_TIMEOUT define

This ifdef isn't referenced anywhere in the code anymore.

R=pdr

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

git-svn-id: svn://svn.chromium.org/blink/trunk@153966 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Merge Node::attach's whitespace fixup loop into recalcStyle

There's no reason to run the whitespace fixup loop in Node::attach if we're in the middle of a
recalcStyle since we'll visit siblings of the node being attached in a future iteration of the loop.
To make this work we need to track which nodes went through a reattach during recalcStyle and
then reattach all their sibling text nodes that are whitespace.

This avoids the O(n^2) behavior across the child nodes when doing lazyAttach as we'll do
from the parser in the future, or as we do right now when calling appendChild() many
times from JS. This will also clean up RenderText 0x0 when you remove an element that was
before a whitespace text node.

R=eseidel@chromium.org, ojan@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@153967 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove CSSGradientValue & ElementStyleResources StyleResolverState deps

CSSGradientValue and ElementStyleResources currently depend on
StyleResolverState for the color resolution logic. Now that it no
longer depends on the state these classes can be updated to call into
TextLinkColors directly.

R=eseidel@chromium.org
BUG=259111

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

git-svn-id: svn://svn.chromium.org/blink/trunk@153968 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Do not fire beforeload events from frames with scripting disabled

This patch fixes a crash where an SVG CSS background image could cause
all pending beforeload events to fire. This became problematic once data
uri images started firing synchronously. The events we are interested in
preventing are global pending beforeload events because they are cross-
document and could be fired from an inner (sandboxed) SVG document.

This patch disables beforeload events from frames where scripting is disabled.

This is a followup to https://src.chromium.org/viewvc/blink?view=rev&revision=153029
which missed this case in XMLDocumentParser.cpp. I have verified the
other global pending event handlers are not called elsewhere.

BUG=256013

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

git-svn-id: svn://svn.chromium.org/blink/trunk@153969 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Replace angle_path gyp variable with regular path.

The switch to angle_dx11 is complete. This is cleanup. These are only the Blink changes.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@153970 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Setting up OrderIterator shouldn't require an extra Vector

This change reuses the OrderIterator's Vector for fun and profit.
The idea is to have an helper class OrderIteratorPopulator, used for
manipulating the Vector directly.

The helper class has the nice upside of consolidating the code into a
single implementation across flexbox and grid.

Also tweaked the Vector to have an inline capacity for a single entry
that will cover the common case.

BUG=256804

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

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