Auto-rebaseline for r172385

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

BUG=364946
TBR=danakj@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172399 bbb929c8-8fbe-4397-9dbb-9b2b20218538
HTML Imports: Teach preloader about HTML Imports.

This change tells HTMLPreloadScanner about <link rel=import> so that
it can preload the resource for the import.

TEST=import-preload.html
R=esprehn@chromium.org,dglazkov@chromium.org
BUG=323096

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172400 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Make data: urls always parse async

Turns out Chrome has long had the behavior of issuing
loads and delivering load events async for data: urls,
but not actually doing the parsing async. This changes
makes the parsing of data:text/html content always async.

NOTE: The new async test (loader/iframe-sync-loads.html)
does not change before before/after this test, it's
there to confirm that we were already behaving async
with regards to when the content appeared in the iframe.

This finally makes it possible to take a JS string
and run it through the HTML parser async.  I'll fix
<iframe srcdoc> to also be async in a follow-up patch.

I wrote a test to check sync/async behavior of various
loading methods for iframes. Gecko has async behavior
for all 3 of these cases in my test, where as Chrome
on Linux has sync behavior for javascript:

This is covered by 3 additional tests:
fast/dom/document-contentType-data-uri.html:
- text/html content is now async, matches FF

accessibility/loading-iframe-sends-notification.html
- had to re-write this test to not assume that the iframe
would be laid out before its onload was fired.

scrollingcoordinator/non-fast-scrollable-region-transformed-iframe.html
- This was hitting crbug.com/365509 which I worked around by
calling setUseMockScrollbars earlier.

BUG=308321, 365509

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172401 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Properly repaint grid item when z-index changes

Previously z-index changes of static positioned objects are ignored.
However, z-index is applicable for some static positioned objects,
such as grid items. Ignoring them makes the object not properly painted
on z-index change.

As StyleAdjuster has ensured that z-index is non-auto only if
applicable, RenderStyle::visualInvalidationDiff() should not check
again (with inconsistent conditions).

BUG=234200
TEST=fast/css-grid/layout/grid-item-z-index-change-repaint.html

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=172168

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172402 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Add a watchlist for myself in dom/ and rendering/

NOTRY=true

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172403 bbb929c8-8fbe-4397-9dbb-9b2b20218538
[CSS Grid Layout] Add GridSpan::iterator

As suggested when GridResolvedPosition was introduced, this patch
adds a GridSpan::iterator which allows to simplify the loops over
GridResolvedPositions.

BUG=258258

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172404 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Disable layer squashing

We've gotten a number of interesting bug reports. We're going to disable this
feature on trunk while we work through the bug reports.

This CL adds a new way to disable layer squashing via RuntimeEnabledFeatures.
This mechanism lets us leave the feature turned on for the LayoutTests so we
don't need to keep rebaselining them when we turn the feature on and off.

R=chrishtr@chromium.org
BUG=365701

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172405 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove dead code from RenderEmbeddedObject

Since canHaveChildren() is always false in this function, everything
after the !canHaveChildren() check in layout() is a no-op.
RenderPart::layout() is also a no-op except for clearing the needsLayout
bit (which RenderEmbeddedObject does itself anyway) so remove that too.
Finally all the overrides of the RenderObjectChildList were unused, so
remove them too.

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172406 bbb929c8-8fbe-4397-9dbb-9b2b20218538
document.open(): gracefully handle exception thrown on window.open access.

Check if the "open" property lookup on the global object returned anything
before attempting to use it.

R=haraken@chromium.org
BUG=365659
TEST=fast/js/document-open-getter-throw-no-crash.html

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172407 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove main frame overflow from some binary non-scrollbar tests

These were split out from https://codereview.chromium.org/249723003
because they are binary files and the CQ can't apply patches with them
in it.

BUG=361729
R=abarth@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172408 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Setting RL's grouped mapping should remove it from the old one.

Currently, when a RenderLayer is assigned to a new grouped
mapping for squashing, updateGroupedMapping will only mark
the old grouped mapping as needing a graphics layer update.
The old grouped mapping will, however, retain a raw pointer
to the RenderLayer.

It turns out that it is possible to get the old grouped
mapping to use this raw pointer, so it's important that we
clear it when we switch backings so that this never happens.

The attached test case triggers this use of one of these
stale pointers, but it's clunky. It should be possible to
get a better repro.

R=abarth@chromium.org
BUG=365064

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172409 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Fixed crash when restoring contexts which had previously been forcibly lost

BUG=365747

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172410 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Test for crash on mobile Google maps

This CL contains a test for https://codereview.chromium.org/248093002/. I'm
landing the test and the fix separately to make sure that the fix is available
in tomorrow's canary build.

R=chrishtr@chromium.org
BUG=365597

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172411 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove deprecated WebFrameClient methods, part 1/2.

BUG=361761
TEST=everything stays green

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172412 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Allow text autosizer to repaint during performLayout.

The performLayout method has two sections where the actual layout() is done.
Between those two sections it's possible for the text autosizer to set style
on a render object which will trigger a repaint(). This CL explicitly enables
this behaviour by wrapping the autosizer call in an AllowRepaintScope.

BUG=320139

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172413 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Ensure that painting phases are updated correctly in the CLM

Currently, we rely on ad hoc code to reset painting phases for our
graphics layers as the internal hierarchy changes. This is brittle and
leads to bugs, both when we set the wrong painting phases (or fail to
set them) as well as when we fail to invalidate layers when their paint
phases change.

This CL consolidates the painting phase updates for layers whose paint
phases vary depending on the hierarchy, and puts code in place to
trigger invalidations when these phases do indeed change.

R=enne@chromium.org
BUG=361940

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172414 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove Hack used in blink side for merging dependent chromium and blink patches.

To merge the dependent patches https://codereview.chromium.org/137893025/ and https://codereview.chromium.org/138523003/ ,
older definition of the function didActivateCompositor() was also needed to be kept at both chromium and blink side.
This was introduced in https://codereview.chromium.org/189263019/ . Since all of the patches have landed now, we can land this final patch which removes the older definitions from the blink side.

BUG=None
TBR=jamesr@chromium.org

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

git-svn-id: svn://svn.chromium.org/blink/trunk@172415 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Add <label> to items in Event Listener Breakpoint of Chrome Dev Tools

At present, when attempting to set an event listener breakpoint
within the Event Listener Breakpoint section of the Sources
tab of Chrome Dev Tools, you must click on the checkbox.

This CL adds a <label> so a user can simply click on the associated
text and the checkbox will be clicked.

BUG=360404

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

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