Add Kenneth Rohde Christiansen to core OWNERS

Congratulation, Kenneth!

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

git-svn-id: svn://svn.chromium.org/blink/trunk@159580 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Revert 159282 "Refactor fixed layout mode"

> Refactor fixed layout mode
>
> Previously, the desktop browser would use FrameView's rect
> as the layout size while the mobile browser would enable
> "fixed layout mode" which then used a layoutSize variable
> that it could set instead.
>
> This CL removes "fixed layout mode" as a FrameView concept
> and makes the layout size always an explicitly set property
> of the main FrameView. Another way to think about it is that
> we're now always in a fixed-layout, only we keep
> the layout size pegged to the window size (if the
> --enable-viewport flag is set, the layout size is set from
> @viewport/viewport meta).
>
> Note: WebViewImpl still has a setFixedLayoutSize method
> that's used by Android WebView.
>
> This patch relands https://codereview.chromium.org/23819019/
> which caused an autosize related browser test break.
>
> BUG=285397
>
> Review URL: https://codereview.chromium.org/26546006

TBR=bokan@chromium.org
BUG=306566

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

git-svn-id: svn://svn.chromium.org/blink/trunk@159581 bbb929c8-8fbe-4397-9dbb-9b2b20218538
Remove layerForScrollChild / layerForScrolling

These methods were either never used or used
as part of the ScrollableArea interface.

BUG=260899

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

git-svn-id: svn://svn.chromium.org/blink/trunk@159582 bbb929c8-8fbe-4397-9dbb-9b2b20218538
[CSSRegions] Create auto-size folder and move related regions tests

Create fast/regions/auto-size folder and move autosize* and autowidth* tests.
Will move autoheight* in a follow-up patch.

BUG=306369

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

git-svn-id: svn://svn.chromium.org/blink/trunk@159583 bbb929c8-8fbe-4397-9dbb-9b2b20218538
[CSS Regions] Activate all regions to have layers, as CSS Regions create
a new stacking context

The CSS Regions specification says "CSS Regions create a new stacking
context." (http://dev.w3.org/csswg/css-regions/).

Divs that create stacking contexts are painted after the divs that don't
create stacking contexts.

For the ref tests, the divs in the expected results corresponding to the
regions now have a CSS style causing them to also create Stacking
Contexts.

While the region-sibling-paint-order.html test verifies that regions
paint correctly when the next sibling also creates a stacking context,
tacking-context-paint-order.html verifies that regions paint correctly
when the next sibling doesn't create a stacking context.

Ported from http://wkb.ug/121828

The patch also includes the following fixes by Mihnea Ovidenie that are
related to the issue (CSS Regions creating Stacking Contexts):
http://wkb.ug/122405 Computed z-Index should return 0 instead of auto
for a region
http://wkb.ug/122389 Regions with overflow: hidden should paint over
positioned sibling
http://wkb.ug/122321 Regions as stacking contexts should paint over
positioned sibling
http://wkb.ug/122543 Use RenderStyle::hasStyleRegion when needed

BUG=303026

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

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