GitLab

Fling event is sent to the same target that the last scroll event
was sent to.

BUG=698260

Review-Url: https://codereview.chromium.org/2808723003
Cr-Commit-Position: refs/heads/master@{#464419}

In crrev.com/2811003002, some methods were renamed which they shouldn't.
This CL changes them back.

BUG=40407, 179576

Review-Url: https://codereview.chromium.org/2812983005
Cr-Commit-Position: refs/heads/master@{#464418}

Replacing 'profile manager' with 'user manager' for consistency.

BUG=707828

Review-Url: https://codereview.chromium.org/2815133002
Cr-Commit-Position: refs/heads/master@{#464417}

TBR=bradnelson@chromium.org
BUG=711289

Review-Url: https://codereview.chromium.org/2817013002
Cr-Commit-Position: refs/heads/master@{#464416}

This fixes a crash when exiting VR.

BUG=None

Review-Url: https://codereview.chromium.org/2814843008
Cr-Commit-Position: refs/heads/master@{#464415}

Automatically generated ARCMigrate commit
Notable issues:None
BUG=624363
TEST=None

Review-Url: https://codereview.chromium.org/2815513008
Cr-Commit-Position: refs/heads/master@{#464414}

To unblock https://skia-review.googlesource.com/c/13198/

R=reed@google.com
NOTRY=true

Review-Url: https://codereview.chromium.org/2810333006
Cr-Commit-Position: refs/heads/master@{#464413}

This CL adapts the M59 defaults for remote suggestions scheduler to
observations from M57 soft fetches rollout. It also, targetting EM, sets
cellular soft interval values to 2x of corresponding wifi values.

BUG=672479

Review-Url: https://codereview.chromium.org/2809263006
Cr-Commit-Position: refs/heads/master@{#464412}

Add a map to set different minimum output buffer size per board.
We can use smaller minimum output buffer size for powerful board, and
use larger minimum output buffer size for slower board.

BUG=581679
TEST=On kevin board, check block size is 768 on WebAudio test page.
TEST=On samus board, check block size is 256 on WebAudio test page.

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2787433002
Cr-Commit-Position: refs/heads/master@{#464411}

TBR=jdoerrie@chromium.org
BUG=710864

Review-Url: https://codereview.chromium.org/2808273007
Cr-Commit-Position: refs/heads/master@{#464410}

R=ellyjones@chromium.org

Review-Url: https://codereview.chromium.org/2820523002
Cr-Commit-Position: refs/heads/master@{#464409}

When (animated attribute) mutations are trigger by a 'id' change (via
an IdTargetObserver), relative lengths state may be revalidated while
the element are in the process of being removed from the document, but
has not yet been marked as such. If relative length state is updated in
such a case, the |elements_with_relative_lengths_| set could end up in
an inconsistent state.
Instead of only relying on the connected bit of the current element,
also check all the ancestors to make sure.

BUG=705200

Review-Url: https://codereview.chromium.org/2817913002
Cr-Commit-Position: refs/heads/master@{#464408}

TBR=sebsg@chromium.org
BUG=595385

Review-Url: https://codereview.chromium.org/2819553002
Cr-Commit-Position: refs/heads/master@{#464407}

BUG=swiftshader:32
TBR=kbr@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2814073004
Cr-Commit-Position: refs/heads/master@{#464406}

Reland of https://codereview.chromium.org/2796303006/.
Original CL description:

Add gesture (touch) support in views::ResizeArea, which
is used for resizing the location bar. This area is located
directly to the right of the location bar.

BUG=320544
TEST=ResizeAreaTest.*

Review-Url: https://codereview.chromium.org/2818483002
Cr-Commit-Position: refs/heads/master@{#464405}

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/41bda73617ed..4709b3a00e51

$ git log 41bda7361..4709b3a00 --date=short --no-merges --format='%ad %ae %s'
2017-04-13 nednguyen Revert of [web-page-replay] Roll WPR to the latest commit (patchset #1 id:1 of https://codereview.chromium.org/2811373002/ )

Created with:
  roll-dep src/third_party/catapult
BUG=711232


Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls


CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=sullivan@chromium.org

Change-Id: I22cdb7239652c5db664e44ce30664733e508f2c9
Reviewed-on: https://chromium-review.googlesource.com/476870
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#464404}

Revert of When HttpNetworkTransaction encounters QUIC errors, retry the request (patchset #3 id:40001 of https://codereview.chromium.org/2818623002/ )

Reason for revert:
Likely cause of compilation error in Win x64.

BUG=711316

Original issue's description:
> When HttpNetworkTransaction encounters QUIC errors, retry the request
> with alt-svc disabled, and if that succeeds then mark QUIC as broken.
>
> Protected by the retry_without_alt_svc_on_quic_errors finch param.
>
> BUG=705033
>
> Review-Url: https://codereview.chromium.org/2818623002
> Cr-Commit-Position: refs/heads/master@{#464391}
> Committed: https://chromium.googlesource.com/chromium/src/+/d0dbccf1f8d23dfa32defdd02c0a3df990729358

TBR=jri@chromium.org,ianswett@chromium.org,rch@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=705033

Review-Url: https://codereview.chromium.org/2811993005
Cr-Commit-Position: refs/heads/master@{#464403}

Codes are used internally only right now. Authpolicy shouldn't
actually send them yet. This might be implemented in a future CL.

BUG=chromium:676607
TEST=Squinted eyes to make sure XML is valid.

Review-Url: https://codereview.chromium.org/2809413002
Cr-Commit-Position: refs/heads/master@{#464402}

When ChromeDriver sets focus on an element, a descendant node of
that element may receive the focus instead. Modifying ChromeDriver
code to handle such a case.

Review-Url: https://codereview.chromium.org/2813043003
Cr-Commit-Position: refs/heads/master@{#464401}

TBR=mtomasz@chromium.org
BUG=711290

Review-Url: https://codereview.chromium.org/2815293003
Cr-Commit-Position: refs/heads/master@{#464400}

For them to compile when copy-pasted (proper base:: prefixes and avoiding
english logic in code example).

BUG=667892
NOTRY=true

Review-Url: https://codereview.chromium.org/2815463003
Cr-Commit-Position: refs/heads/master@{#464399}

Add fuzzer that reads test input and creates a color profile
from it (or bails if not). Given that profile |test|, create
another profile |srgb| used to transform colors to/from when
running the color transform fuzzer test stage.

Test ICC version 2 profiles only since ICC version 4 support
in QCMS is not enabled in Chrome.

Add third_party/qcms/DEPS: allows qcms_color_space_fuzzer to
use //base and //testing code.

Speed: achieves ~2300 execs/s on Mac Air. Seed corpus of ICC
profiles uploaded to qcms_color_space_fuzzer GCS bucket.

Set max_len to 4Meg (color profiles can be large and this is
the limit that Chrome accepts), and use the ICC profile dict
added in http://crrev.com/461603

TBR=inferno@chromium.org
BUG=708016

Review-Url: https://codereview.chromium.org/2807083002
Cr-Commit-Position: refs/heads/master@{#464398}

This test is failing after a chromium roll. Temporary disable it for
a greener tree.

BUG=711291

Review-Url: https://codereview.chromium.org/2816023003
Cr-Commit-Position: refs/heads/master@{#464397}

Both SettingsEasyUnlockBrowserTest.EasyUnlock and SettingsUIBrowserTest.All are flaky on Release builds.

TBR=dpapad@chromium.org
BUG=711256

Review-Url: https://codereview.chromium.org/2815513010
Cr-Commit-Position: refs/heads/master@{#464396}

We have two code paths that download favicons from different favicon
servers. We can switch between them based on a field trial feature.

This CL adds logging of success rates for both the code-paths.

BUG=709498

Review-Url: https://codereview.chromium.org/2812243002
Cr-Commit-Position: refs/heads/master@{#464395}

If disable_ffmpeg_video_decoders is set to true on platfoms other
than Android ffmped_video_decoder.* is always included.
This patch removes those sources and fixes dependencies in code.

Review-Url: https://codereview.chromium.org/2808093008
Cr-Commit-Position: refs/heads/master@{#464394}

BUG=583292

Review-Url: https://codereview.chromium.org/2814753002
Cr-Commit-Position: refs/heads/master@{#464393}

BUG=

Review-Url: https://codereview.chromium.org/2810663002
Cr-Original-Commit-Position: refs/heads/master@{#463247}
Committed: https://chromium.googlesource.com/chromium/src/+/e206dbe248c7727f81424d6b89274a52def52e6a
Review-Url: https://codereview.chromium.org/2810663002
Cr-Commit-Position: refs/heads/master@{#464392}

with alt-svc disabled, and if that succeeds then mark QUIC as broken.

Protected by the retry_without_alt_svc_on_quic_errors finch param.

BUG=705033

Review-Url: https://codereview.chromium.org/2818623002
Cr-Commit-Position: refs/heads/master@{#464391}

This is a roll-back to 5.9.211. This is the most stable candidate out of the latest Canaries.

If this commit results in failures in Blink please contact the Blink sheriff. They may need to make changes to Blink because of the roll-back.

When in doubt please try to contact the committer and reviewers of this CL before reverting it.

TBR=machenbach@chromium.org

Review-Url: https://codereview.chromium.org/2822443002
Cr-Commit-Position: refs/heads/master@{#464390}

BUG=none
R=rohitrao@chromium.org

Review-Url: https://codereview.chromium.org/2812133004
Cr-Commit-Position: refs/heads/master@{#464389}

The call to WTSQuerySessionInformation can take arbitrary long time and thus
can crash the browser when it takes more then expected. This even if not
crashing the browser also was stalling the FILE thread.

BUG=706737
TEST=Wait and see if crash rate falls.

Review-Url: https://codereview.chromium.org/2814793005
Cr-Commit-Position: refs/heads/master@{#464388}

There is no android:action in intent-filter:
https://developer.android.com/guide/topics/manifest/intent-filter-element.html

This causes errors in Android Studio when including this
AndroidManifest.

BUG=620034

Review-Url: https://codereview.chromium.org/2815083002
Cr-Commit-Position: refs/heads/master@{#464387}

This CL adds the functionality to open the 4 search modes in the main
application: regular, incognito, voice and qr code. UI support will be
in a future CL.

BUG=622743

TBR=jif

Review-Url: https://codereview.chromium.org/2809173002
Cr-Commit-Position: refs/heads/master@{#464386}

Previously, accepting EULA issued a browser-foregrounded trigger. This
trigger is now ignored on default in release channels.

This CL changes it to persistent fetch trigger so that we are sure the
initial fetch is performed, no matter how we change the params in the
future.

BUG=676662

Review-Url: https://codereview.chromium.org/2817903003
Cr-Commit-Position: refs/heads/master@{#464385}

This is partly rollback of http://crrev.com/2702313002
While content of policy compliance report is not important for
starting kiosk app, ChromeOS should wait for compliance report
from CloudDPC side to ensure that all permissions are already
correctly granted before app is started.

BUG=b/36678353
TEST=ArcPolicyBridge unittests

Review-Url: https://codereview.chromium.org/2809773004
Cr-Commit-Position: refs/heads/master@{#464384}

The catapult CL [1] will introduce a change where running adb commands
may now raise device_errors.DeviceUnreachableError if the device is
no longer found.

This change adjusts clients that were hoping to catch this kind of
error as a device_errors.[Adb]CommandFailedError.

[1]: https://codereview.chromium.org/2808763004/

BUG=https://github.com/catapult-project/catapult/issues/3476

Review-Url: https://codereview.chromium.org/2811993002
Cr-Commit-Position: refs/heads/master@{#464383}

The old Delegate API made it rather awkward to get at the full details of
the request.  This new API fixes that, whilst allowing more flexible
request modification.

BUG=546953

Review-Url: https://codereview.chromium.org/2815003003
Cr-Commit-Position: refs/heads/master@{#464382}

This CL switches the content/browser/ part of offscreen canvas to use
FrameSinkManagerHost instead of directly accessing SurfaceMananger.

OffscreenCanvasProvider(Impl) exists for the renderer to request other
interfaces from the browser. The renderer uses it create both a
OffscreenCanvasSurface and MojoCompositorFrameSink. This is a
simplification of OffscreenCanvasCompositorFrameSinkProvider and
OffscreenCanvasSurfaceFactory interfaces.

RenderProcessHostImpl creates a single OffscreenCanvasProviderImpl on
demand and uses it for all offscreen canvas requests from the renderer.

The renderer will first request a OffscreenCanvasSurface and specify the
FrameSinkId. This always happens from the main renderer thread. A
OffscreenCanvasSurfaceImpl will be created for the browser side of this
connection.

The renderer will then likely request MojoCompositorFrameSink for the
FrameSinkId, from either the main thread or a worker thread. This
request is forwarded to MojoFrameSinkManager. This sets up two
connections. There is a MojoCompositorFrameSink from
MojoFrameSinkManager to the renderer. This is used to submit
CompositorFrames. There is MojoCompositorFrameSinkPrivate from
OffscreenCanvasSurfaceImpl to MojoFrameSinkManager. This gives the
browser control over the CompositorFrameSink created in
MojoFrameSinkManager.

The render can close the OffscreenCanvasSurface and
MojoCompositorFrameSink connections in any order. The assumption is they
will both be closed at approximately the same time.

The remaining direct access to SurfaceManager by offscreen canvas code
is blocked on other features being completed.

BUG=664547,686861
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation

Review-Url: https://codereview.chromium.org/2789753002
Cr-Commit-Position: refs/heads/master@{#464381}

Skipping tasks when destroying ScopedTaskEnvironment or
ScopedAsyncTaskScheduler means that DeleteSoon() tasks
can be skipped, resulting in memory leaks.

BUG=708584, 709095

Review-Url: https://codereview.chromium.org/2812293002
Cr-Commit-Position: refs/heads/master@{#464380}