GitLab

BUG=

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

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

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/27a38796..627ffe9a

Please follow these instructions for assigning/CC'ing issues:
https://code.google.com/p/v8-wiki/wiki/TriagingIssues

TBR=machenbach@chromium.org

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

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

Add a new enable_nonblocking_io field trial param for QUIC which enables the new non-blocking IO support on windows.

BUG=442392

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

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

This applies the same approach as r318190 to clean up
stale generated java when any mojom dependencies have
changed in gyp targets using
mojom_bindings_generator_explicit.gypi.

BUG=461622
R=jamesr@chromium.org

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

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

Implemented stub FindChrome() on android that does nothing
and returns false.

BUG=462434

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

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

Some of the tests weren't properly instantiating a PrefService. It's now being
done in the ExtensionServiceTestBase class and its subclasses were modified
where needed.

BUG=461484

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

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

The ui browser compositor should use onecopy for implside painting, as
we have enabled that for all platforms that use ui::Compositor.

The image texture target should also match the one used in the renderer
compositor. So have the ui::Compositor query it from the ContextFactory
and move the code that makes the decision out from RenderProcessHostImpl
to a shared location.

R=piman@chromium.org, reveman
BUG=314185

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

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

Added PresentationSession Mojo interface with its client implementation, PresentationSessionDispatcher.
Depends on the Blink change: https://codereview.chromium.org/935103002

BUG=459005

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

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

This makes aura_demo output show up.

R=piman@chromium.org
BUG=462739

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

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

BUG=452218
TEST=Go to chrome://interstitials and click on "Clock is ahead" or "Clock is behind". The shown interstitial displays the clock error message instead of the common certificate warning.

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

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

on desktop, as it is on mobile.

BUG=none

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

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

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/4f569be..394ce76

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

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

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

Revert of Add remoting and PPAPI tests to GN build (patchset #7 id:120001 of https://codereview.chromium.org/965633002/)

Reason for revert:
http://build.chromium.org/p/chromium.mac/buildstatus?builder=Mac%20GN&number=4498

ERROR at //remoting/host/BUILD.gn:56:7: Item not found
      "linux/x_server_clipboard.cc",
      ^----------------------------
You were trying to remove "linux/x_server_clipboard.cc"

Original issue's description:
> Add remoting and PPAPI tests to GN build
>
> BUG=
>
> Committed: https://crrev.com/d0437210926b14b1b7e06b2b56174fc92ade9c37
> Cr-Commit-Position: refs/heads/master@{#318539}

TBR=kelvinp@chromium.org,dpranke@chromium.org,brettw@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=

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

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

This makes the components_unittests pass.

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

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

BUG=461509

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

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

Adds a way to stop InfoBars and SwipableOverlayViews from auto-hiding.

BUG=452614

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

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

The fix for issue 176725 is suspected to introduce this crash.
Implement an alternative workaround that taps the mouse moved
events from the application's event stream.

BUG=315379
TEST=See http://crbug.com/176725

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

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

BUG=460412

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

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

BUG=

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/e19522f..6c51e22

TBR=hclam@chromium.org,alancutter@chromium.org

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

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

* Exposing MessageReceived as virtual on GCMDriver so that it can be
called from outside of GCMClientImpl (through IOWorker)
* Adding handling of gcmb key to GCMAccountMapper
* Adding a test for dispatching the message from GCMAccountMapper

BUG=462053
R=zea@chromium.org

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

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

Chunked upload support is added for embedded_test_server, so we should
enable chunked upload in CronetUrlRequest since now we have testing support.

BUG=412942

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

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

This prevents filtering out key release events, resulting in stuck keys.

BUG=449162
TEST=Fully rotate glimmer while holding spacebar. No spurious
  key repeats.

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

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

In the CSS, this name is used for an ID, but in the JS side
this name is used for a class name, it seems this name is just
unused.

It would be okay to use this as a class name, but this specifies
margin only, and we don't see any claims about margin for mirroring
view. Actually, mirroring displays are centered and sized well,
so nobody notices the margin for the container. Let's just remove
unused code.

BUG=None
R=dbeam@chromium.org

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

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

We didn't have any metric for measuring Android UI animation jankiness
before, and recently it came to our attention that animations are very
janky on some low-end devices. It will be useful to know how the
animations are doing on various user devices.

This class can be used to record animation frame times histogram,
for example:

AnimationFrameTimeHistogram histogram =
        new AnimationFrameTimeHistogram(HISTOGRAM_NAME);
histogram.startRecording();
// An animation to measure
histogram.endRecording();

or

animator.addListener(AnimationFrameTimeHistogram.getAnimatorRecorder(
        HISTOGRAM_NAME);

To my knowledge, the closest thing we have is measuring each task
runtime using TaskStopwatch class, but that doesn't suit for us since
Android animation frame tasks are managed by Android, and even if we
can use, it will require a JNI call for each frame.

BUG=461066

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

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

The CL https://codereview.chromium.org/943823002/ introduced a new
histogram for whether web pages are assumed to be mobile friendly.

However, there was a typo in recording the histogram name.

This fixes the recording part to match the histogram.

BUG=462721

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

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

Also adds more fields to environment to narrow the scope of
benchmark and user story set discovery. This should avoid problems
with adding Python files to unrelated directories, and hides PageTests
from external Telemetry benchmark runners like run_gpu_tests.py and
chrome_proxy's run_benchmark.

R=dtu,nednguyen,sullivan,kbr@chromium.org,bolian
BUG=460181
TEST=tools/perf/run_benchmark; content/test/gpu/run_gpu_tests.py; tools/chrome_proxy/run_benchmark  # All return a full and correct test list.

Committed: https://crrev.com/1da5f7f70ea6dc7dd0667ea78637802c76305f5a
Cr-Commit-Position: refs/heads/master@{#318149}

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

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

It's unused and will probably never go stable. Delete it; we can pull it
from source control later if we change our minds.

TBRing thestig for chrome/common/ppapi_utils, and binji for native_client_sd
BUG=83774
TBR=thestig@chromium.org,binji@chromium.org

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

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

Reland of https://codereview.chromium.org/958743003/
TBR=dpranke

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

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

Revert of Splitting of layers for correct intersections (patchset #17 id:310001 of https://codereview.chromium.org/595593002/)

Reason for revert:
Static initializers count increased

Original issue's description:
> Splitting of layers for correct intersections
>
> Sorting 3d-sorted layers and rendering them in that order causes issues
> when layers intersect. Instead place 3d-sorted layers in a bsp tree and
> fragment any intersecting layers into non-rectangular quads. We can then
> render the fragments in the correct sorted order regardless of
> intersections.
>
> BUG=455918,159225,132122,230833
>
> Committed: https://crrev.com/ac754705ceaa5bc4cb8dc8df9a733b4b68396399
> Cr-Commit-Position: refs/heads/master@{#318506}

TBR=enne@chromium.org,danakj@chromium.org,thakis@chromium.org,awoloszyn@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=455918,159225,132122,230833

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

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

Revert of Clean up the top level BUILD.gn file. (patchset #2 id:20001 of https://codereview.chromium.org/963093003/)

Reason for revert:

ERROR at //BUILD.gn:246:7: Item not found
      "//third_party/usrsctp",  # TODO(GYP)
      ^----------------------
You were trying to remove "//third_party/usrsctp"

Original issue's description:
> Clean up the top level BUILD.gn file.
>
> There was a bunch of todo-related stuff that could
> be cleaned up, and this change also removes the 'gyp_all'
> target which was mostly just duplicating stuff in all.gyp.
>
> This CL should have no actual affect on the builds, apart
> from deleting the one target, but is also a prelude to
> subsequent CLs for this bug.
>
> R=brettw@chromium.org
> BUG=461019
>
> Committed: https://crrev.com/18e5743bbe39f30b75abad4c5c7f0efab288ed9a
> Cr-Commit-Position: refs/heads/master@{#318523}

TBR=brettw@chromium.org,dpranke@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=461019

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

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

BUG=411251,368525

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

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

Getting and updating the load state of requests is janky.

TBR=eroman@chromium.org
BUG=455952

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

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

mips_dsp_rev specifies the MIPS DSP ASE (Application-Specific
Extension) revision number. Possible values are 0 (unavailable), 1,
and 2. Default to 0.

mips_float_abi specifies whether or not MIPS floating-point coprocessor
instructions should be used. Possible values are "hard" and "soft".
Default to "hard".

mips_fpu_mode specifies the width of MIPS32 floating-point registers.
Possible values are "fp32", "fp64", and "fpxx". Default to "fp32".

The companion webrtc CL is
https://webrtc-codereview.appspot.com/39779004.

R=brettw@chromium.org,kjellander@@chromium.org,petarj@mips.com
BUG=446234

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

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

There was a bunch of todo-related stuff that could
be cleaned up, and this change also removes the 'gyp_all'
target which was mostly just duplicating stuff in all.gyp.

This CL should have no actual affect on the builds, apart
from deleting the one target, but is also a prelude to
subsequent CLs for this bug.

R=brettw@chromium.org
BUG=461019

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

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

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/9888b22..4f569be

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

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

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

Summary of changes available at:
https://chromium.googlesource.com/chromium/blink/+log/e79fc23..e19522f

TBR=hclam@chromium.org,alancutter@chromium.org

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

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

The header include guards should match the file path from root.

These entries were found using a modified version of Eric's
fix-include-guards.py script found attached in
https://code.google.com/p/chromium/issues/detail?id=435361#c7.

BUG=435361
TEST=content_unittests
R=avi@chromium.org
TBR=avi@chromium.org

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

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

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

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

This is the last piece of user-facing "SPDY" string in chrome://net-internals.
Instead of "http2_priority", I propose to change it to "priority", since there
is no ambiguity anyway.

BUG=456986

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

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