GitLab

Replace histogram recording for devices where the chromium android linker
is enabled with the following:

  ChromiumAndroidLinker.BrowserStates
    Whether relro sharing was attempted for the browser process, and if
    attempted, whether it succeeded. (0=normal load, 1=low memory load
    with shared relro, 2=low memory load used backoff so no shared relro)

  ChromiumAndroidLinker.RendererStates
    Whether relro sharing was attempted for a renderer process, and if
    attempted, whether it succeeded. (0=load with shared relro, 1=load
    used backoff so no shared relro, 2=shared relro not attempted)

If the chromium android linker is not enabled, none of the above
histograms is recorded.

BUG=419010

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

Cr-Commit-Position: refs/heads/master@{#299291}

Cr-Commit-Position: refs/heads/master@{#299290}

BUG=370175

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

Cr-Commit-Position: refs/heads/master@{#299289}

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/42cab44..194240f

TBR=caseq@chromium.org,apavlov@chromium.org,cbiesinger@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#299288}

The WebView will use a fixed default value for the text encoding instead
of getting it from the platform. This is in attempt to unify behavior
between devices.

BUG=422366

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

Cr-Commit-Position: refs/heads/master@{#299287}

This brings in linux-noasm configs for ChromiumOS and ChromeOS.

BUG=340376
TBR=wolenetz@chromium.org
NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#299286}

BUG=417463

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

Cr-Commit-Position: refs/heads/master@{#299285}

BUG=400440

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

Cr-Commit-Position: refs/heads/master@{#299284}

BUG=422884
TBR=mnissler@google.com

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

Cr-Commit-Position: refs/heads/master@{#299283}

Changes;
-------------------------------------------------------------------------------
Value of: state.NextAction()
  Actual: 1
Expected: SchedulerStateMachine::ACTION_DRAW_AND_SWAP_ABORT
Which is: 8
-------------------------------------------------------------------------------

to

-------------------------------------------------------------------------------
Value of: SchedulerStateMachine::ActionToString(state.NextAction())
  Actual: "ACTION_NONE"
Expected: SchedulerStateMachine::ActionToString( SchedulerStateMachine::ACTION_DRAW_AND_SWAP_ABORT)
Which is: "ACTION_DRAW_AND_SWAP_ABORT"
-------------------------------------------------------------------------------

BUG=416749

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

Cr-Commit-Position: refs/heads/master@{#299282}

BUG=

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

Cr-Commit-Position: refs/heads/master@{#299281}

Add a build of libelf to gn.  Built for host only, as support for
build-time tools.  Not built for targets.

BUG=

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

Cr-Commit-Position: refs/heads/master@{#299280}

Fixes, in clang/gn builds, four occurrences of:
  ../../tools/relocation_packer/src/elf_file.cc: error: unused variable...

BUG=385553

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

Cr-Commit-Position: refs/heads/master@{#299279}

BUG=417463

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

Cr-Commit-Position: refs/heads/master@{#299278}

Due to uninitialized memory.
This CL is fixing the issue.

BUG=408940, 422164, 422472
TEST=Memory bot for content_unittests

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

Cr-Commit-Position: refs/heads/master@{#299277}

BUG=413863
R=sdefresne@chromium.org,erg@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#299276}

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/d3f2504..42cab44

TBR=caseq@chromium.org,apavlov@chromium.org,cbiesinger@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#299275}

TBR=dgozman@chromium.org
BUG=417463

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

Cr-Commit-Position: refs/heads/master@{#299274}

BUG=422871
R=battre@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#299273}

NV_draw_buffers can be used in combination with GLES3.0 to emulate
EXT_draw_buffers. When GLES3.0 and NV_draw_buffers are present, but
native EXT_draw_buffers is not, the extension directive in shaders is
changed in ANGLE to make ESSL 1.00 shaders able to refer to
glFragData[n>0], and DrawBuffersEXT calls are directed to GLES3.0 core
DrawBuffers.

This enables the WEBGL_draw_buffers extension on Tegra K1. Performance
benefits are in the 5-25% range in demos that are able to render both
with and without the WebGL extension.

BUG=421882
TEST=WebGL conformance tests, gpu_unittests

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

Cr-Commit-Position: refs/heads/master@{#299272}

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/488d238..d3f2504

TBR=

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

Cr-Commit-Position: refs/heads/master@{#299271}

BUG=422868
TBR=guohui@chromium.org
NOTRY=true

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

Cr-Commit-Position: refs/heads/master@{#299270}

Make LTHCommon tests to use PictureLayers instead of ContentLayer,
and update the scaling tests to use ideal scales instead of
contents scale accordingly.

BUG=401492

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

Cr-Commit-Position: refs/heads/master@{#299269}

AppKit ignores -[NSView canDrawConcurrently:] and invokes redraws on the
animation thread.

The last attempt to make one part safe was r296591. However,
http://crbug.com/421952 links to undiagnosable crashes within AppKit
from a build at r298667. These are likely race conditions due to this
threading.

The downside is just that, when Chrome is not running, the initial
appearance of the app launcher window will be a bit delayed, and will
just "pop" in, rather than animate.

BUG=421952

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

Cr-Commit-Position: refs/heads/master@{#299268}

BUG=

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

Cr-Commit-Position: refs/heads/master@{#299267}

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/4c20982..488d238

TBR=

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

Cr-Commit-Position: refs/heads/master@{#299266}

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/f355df5..0d76b95

CQ_EXTRA_TRYBOTS=tryserver.blink:linux_blink_rel,linux_blink_dbg
TBR=rmistry@google.com

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

Cr-Commit-Position: refs/heads/master@{#299265}

Suppress failures on Retina Macs. These failures are kicking valid
jobs out of the commit queue. Tested suppression locally.

BUG=422803
TBR=zmo@chromium.org,bajones@chromium.org

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

Cr-Commit-Position: refs/heads/master@{#299264}

Fullscreen is asynchronous on Mac, so NativeWidgetMac needs to
coordinate with the ViewsNSWindowDelegate to behave in the manner views
code expects. Part of this is maintaining the restored bounds, which
Cocoa doesn't provide access to.

Activation also goes through the ViewsNSWindowDelegate. It's simpler but
needs an interactive_ui_test, which is added. Other NSWindowDelegate
messages are deferred to a follow-up.

Maximize is "implemented" as a no-op on Mac, since it's
indistinguishable from a large window (whereas views code typically
expects maximize to remove window borders).

This CL gets the following views_unittests passing:
  WidgetTest.GetRestoredBounds
  WidgetTest.ExitFullscreenRestoreState
  WidgetTest.FullscreenFrameLayout

Many Cocoa-native tests are also added to ensure user-initiated
operations are correctly observed.

BUG=403679, 378134

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

Cr-Commit-Position: refs/heads/master@{#299263}

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/f2bdd18..4c20982

TBR=

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

Cr-Commit-Position: refs/heads/master@{#299262}

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/10f4f8f..f2bdd18

TBR=

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

Cr-Commit-Position: refs/heads/master@{#299261}

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/485557f..f355df5

CQ_EXTRA_TRYBOTS=tryserver.blink:linux_blink_rel,linux_blink_dbg
TBR=rmistry@google.com

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

Cr-Commit-Position: refs/heads/master@{#299260}

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/d27726e..485557f

CQ_EXTRA_TRYBOTS=tryserver.blink:linux_blink_rel,linux_blink_dbg
TBR=rmistry@google.com

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

Cr-Commit-Position: refs/heads/master@{#299259}

Previously InterpolatedScale and InterpolatedTranslation supported only 2d Translate and 2d Scale.
Added support for 3d Translate and Scale.

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

Cr-Commit-Position: refs/heads/master@{#299258}

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/b07aa9c..10f4f8f

TBR=

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

Cr-Commit-Position: refs/heads/master@{#299257}

TBR=cmp@chromium.org
BUG=418096

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

Cr-Commit-Position: refs/heads/master@{#299256}

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/09a1d67..d27726e

CQ_EXTRA_TRYBOTS=tryserver.blink:linux_blink_rel,linux_blink_dbg
TBR=rmistry@google.com

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

Cr-Commit-Position: refs/heads/master@{#299255}

Cr-Commit-Position: refs/heads/master@{#299254}

Like https://codereview.chromium.org/312723003 for win32, extract
the display color profile associated with a screen display device
on mac given rectangular bounds in screen coordinates.

Use gfx::ScreenRectFromNSRect to compute the screen that overlaps
the bounds most to match the gfx::Screen concept of overlap.

Add unit tests for on-screen, partially-on-screen, off-screen and
empty bounds.

Note an sRGB color profile is a common case, especially on win32,
so GetDisplayColorProfile returns true and an empty color profile
in that case. Add a header file comment about that.

TEST=gfx_unittests --gtest_filter="ColorProfileTest*Bounds"
BUG=368694

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

Cr-Commit-Position: refs/heads/master@{#299253}

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/18ea777..09a1d67

CQ_EXTRA_TRYBOTS=tryserver.blink:linux_blink_rel,linux_blink_dbg
TBR=reed@google.com

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

Cr-Commit-Position: refs/heads/master@{#299252}