GitLab

Call it getUnzippedFileRowEntries for less confusion.

Bug: 867738
Change-Id: I0e38e8c41ec0cfc599aaa24b369738ffea3c2f0a
Reviewed-on: https://chromium-review.googlesource.com/1150953Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578197}

This CL adds a new UI for NearOOM intervention v1. The code that actually shows this infobar will be added in the next CL with v1 implementation.

Bug: 867353
Change-Id: I7e0914b76626dc1dbd91dd2098f7864b98e691fd
Reviewed-on: https://chromium-review.googlesource.com/1084144
Commit-Queue: Yuzu Saijo <yuzus@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578196}

With this change we start building Chromium with ThinLTO when targeting
Android. In 64-bit Monochrome builds, the 32-bit binary is also built
with ThinLTO. This change is expected to reduce code size significantly
(in local measurements it reduced the size of MonochromePublic.apk by 2.3MB)
and is a prerequisite for enabling control flow integrity in official
builds.

Note that although this change enables ThinLTO, it does not enable
the cross-TU optimizations normally associated with LTO. Enabling
cross-TU optimizations is a separate project.

On my local machine (a Lenovo P920) libmonochrome.so link times increase
as follows:

         before  after (first link)  after (incremental links)
32-bit    18s          140s                     50s
64-bit    13s          107s                     41s

All known blockers have now been fixed. This CL is likely to uncover
unknown blockers.

Bug: 469376
Change-Id: I8981e17abd50bc5ca00440e0d74dda878c911749
Reviewed-on: https://chromium-review.googlesource.com/1150870
Commit-Queue: Peter Collingbourne <pcc@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578195}

Following bot results are included.
8293 8303 8306 8311 8316 8322 8331 8335

1 lines were removed and 3 lines were deflaked by consecutive
results since 8272.

TBR=eae@chromium.org, mstensho@chromium.org
NOTRY=true

Bug: 591099
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: I7959f8c83cde28a9306df50391518d8898d98896
Reviewed-on: https://chromium-review.googlesource.com/1149667
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578194}

Bug:chromedriver:2515 was blocked by chromium:866606, which is now fixed.
Re-enabling affected tests on Mac, but disabling them for Chrome m69
because the fix for chromium:866606 is not included in the Chrome m69
build used on the waterfall.

Bug: chromedriver:2515
Change-Id: I62025961187f184bdea6d0130c482cfb1a5ce411
Reviewed-on: https://chromium-review.googlesource.com/1150968Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578193}

This reverts commit a49d91b6.

The original commit made SessionRestoreTest.MemoryPressureLoadsNotAllTabs crash.
According to my investigation, it was caused by calling SingleThreadProxy::OnCanDrawStateChanged
on the main thread. To avoid it, this CL makes LayerTreeHostImpl::OnMemoryPressure call
OnPurgeMemory on the impl thread through the Proxy.

Bug: 839687, 860090
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ifaef5bcb4029da8645f393d85313be4637aea994
Reviewed-on: https://chromium-review.googlesource.com/1130567
Commit-Queue: Gyuyoung Kim <gyuyoung.kim@lge.com>
Reviewed-by: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578192}

By design, Bluetooth settings change is disabled on a secondary user.
Previous SystemTray implementation indicated that by showing dimmed
Bluetooth row, but UnifiedSystemTray didn't have feedback on that.

TEST=manual
BUG=858973

Change-Id: I65ac3ccdcf103b91f6403453ef6ac7f0b51d60d3
Reviewed-on: https://chromium-review.googlesource.com/1146536Reviewed-by: Yoshiki Iguchi <yoshiki@chromium.org>
Commit-Queue: Tetsui Ohkubo <tetsui@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578191}

Refresh makes tabs taller, and some themes don't provide a background image of
sufficient height.  Tiling by repeating risks looking bad for themes that e.g.
put a line across the top of tabs.  Mirroring can look bad in a lot of cases
too, but it's better than tiling or doing nothing.

Most of this patch is plumbing to expose per-axis tiling modes.

Bug: 866668
Change-Id: Ia6e00a15146e3eb32cda3c8362de4e83e67a8b7f
Reviewed-on: https://chromium-review.googlesource.com/1147740
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Reviewed-by: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578190}

This adds a second JavaScript API entry point to the Contextual Search
Overlay Panel that can be called from the panel content.

The new API allows changing the Overlay position from one open state
to another, or to close it, but not to open it.

BUG=834864

Change-Id: I4fe222edfcf030cfb086ddbb3ecec5071b5448f4
Reviewed-on: https://chromium-review.googlesource.com/1045178Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Donn Denman <donnd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578189}

This reverts commit 49874bf7.

Reason for revert: caused a crash crbug.com/867359

Original change's description:
> Oilpan: Change slots registration in HeapCompaction
>
> This CL changes the system of slots registration in HeapCompaction.
> As preparing for HeapCompaction with IncrementalMarking, we change a timing of the registration on HashMap that related to slots, from during tracing to during atomic pause.
> So, we add HashSet that registeres traced slots.
>
> Bug: 864425
> Change-Id: Ia63c36abbf160dfea115ebd6c6953c499d895770
> Reviewed-on: https://chromium-review.googlesource.com/1145144
> Reviewed-by: Kentaro Hara <haraken@chromium.org>
> Reviewed-by: Keishi Hattori <keishi@chromium.org>
> Reviewed-by: Takashi Sakamoto <tasak@google.com>
> Commit-Queue: Haruka Matsumura <harukamt@google.com>
> Cr-Commit-Position: refs/heads/master@{#577469}

TBR=tasak@google.com,haraken@chromium.org,keishi@chromium.org,harukamt@google.com

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 864425
Change-Id: Ia60c4361ef2a50c5451e3696b41020ce018e7e7a
Reviewed-on: https://chromium-review.googlesource.com/1150007Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Keishi Hattori <keishi@chromium.org>
Commit-Queue: Haruka Matsumura <harukamt@google.com>
Cr-Commit-Position: refs/heads/master@{#578188}

This prevents multiple button action methods from being triggered at the same time.

Bug: 863007

Change-Id: Ic39f6270fc604eff6aa0fed3c7103123e539b193
Reviewed-on: https://chromium-review.googlesource.com/1150634Reviewed-by: edchin <edchin@chromium.org>
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578187}

SSLPrivateKeyInternal owns mojom::SSLPrivateKey, and mojom::SSLPrivateKey
has a reference to SSLPrivateKeyInternal. That keeps both of them alive
until a connection error happens.

This CL removes the reference from mojom::SSLPK to SSLPKI to remove the
cycle.

Bug: 866456
Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: Iab0a8bcd16663520873b6b7b29d9326755d93600
Reviewed-on: https://chromium-review.googlesource.com/1148095Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Taiju Tsuiki <tzik@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578186}

This is prep work to support animations in which the pending query will
animate from the bottom of its parent to the top of its parent on
commit.

Previously, we used two distinct views to represent a pending query and
a committed query, respectively.

Now, the same view will be used for a query thoughout its lifecycle.
This will allow us to animate it when committed.

This CL does NOT animate the view, just prepares for animating in a
follow up CL.

Bug: b:110228421
Change-Id: I119db0d4be48960bc13db04caeee4529d240e41d
Reviewed-on: https://chromium-review.googlesource.com/1149002
Commit-Queue: David Black <dmblack@google.com>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578185}

Bug: 853863
Change-Id: I15224eb329160dba1c558bc0a89f97c203f9f05f
Reviewed-on: https://chromium-review.googlesource.com/1140737
Commit-Queue: Nick Harper <nharper@chromium.org>
Reviewed-by: Eric Lawrence <elawrence@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578184}

https://webrtc.googlesource.com/src.git/+log/68936b1f34e6..625efe6dfe5b


git log 68936b1f34e6..625efe6dfe5b --date=short --no-merges --format='%ad %ae %s'
2018-07-25 qingsi@google.com Use also the related address in redundancy detection for candidates from
2018-07-25 buildbot@webrtc.org Roll chromium_revision 17efa884..d6ce677a (577964:578078)


Created with:
  gclient setdep -r src/third_party/webrtc@625efe6dfe5b

The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng

BUG=chromium:None
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: I8043ba67f3cd9fd74a2e9bef889637b248e8b66c
Reviewed-on: https://chromium-review.googlesource.com/1150371Reviewed-by: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#578183}

Add tests cases for unzipping a zip archive from Downloads, Drive, and
a removable volume (USB).

Test: browser_tests --gtest_filter="ZipFiles/FilesApp*"
Bug: 864256,865197,867738
Change-Id: Iea2d2a8537798d7eb4eab7370862fe27a4054a7e
Reviewed-on: https://chromium-review.googlesource.com/1150008Reviewed-by: Tatsuhisa Yamaguchi <yamaguchi@chromium.org>
Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578182}

This reverts commit 556813c9.

Reason for revert: LeakSanitizer detected memory leaks
https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8940004334055018640/+/steps/content_unittests__with_patch_/0/logs/VideoTrackRecorderTest.HandlesOnError/0

Original change's description:
> [Media Recorder] Fix video freeze on short recording. Fix tab crash on initialize.
> 
> Fixes an issue where VideoTrackRecorder when used in combination with
> VEAEncoder and very short recording durations (just 1 frame) would
> occasionally hold on to video frames forever, causing frame buffers
> from the buffer pool to become permanently blocked, eventually leading
> to video capture freezing.
> 
> The cause was a circular ownership that would happen if only 1 frame
> is recorded.
> 
> This CL additionally fixes a crash that could happen on initialization
> of VEAEncoder. This issue was revealed during testing of the above fix.
> Since it is not 100% if this crash was masked by the other issue, and
> would only start occurring with the above fix, I am making a fix for that
> part of this CL as well.
> 
> The cause for the crash issue was that class VEAEncoder, which uses
> RefCountedThreadSafe<>, would post an asynchronous task from its
> constructor. If this task would finish executing before the newly
> constructed instance was assigned to a scoped_refptr<> by however
> called the constructor, the instance would destroy itself, because
> of the AddRef() and subsequent Release() done by the posting and
> running of the asynchronous task.
> 
> The fix for this is to use a new method Initialize() instead of
> posting a task from the constructor.
> 
> Bug: 859610
> Change-Id: I6645aebfaa7659ab0ced0a20fae57eedfb9d84ab
> Reviewed-on: https://chromium-review.googlesource.com/1145877
> Commit-Queue: Christian Fremerey <chfremer@chromium.org>
> Reviewed-by: Emircan Uysaler <emircan@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#577735}

TBR=emircan@chromium.org,chfremer@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 859610,867625
Change-Id: If3fed5676c76da0d6b6ef6a041d74c782e87ebf3
Reviewed-on: https://chromium-review.googlesource.com/1150947Reviewed-by: Yoichi Osato <yoichio@chromium.org>
Commit-Queue: Yoichi Osato <yoichio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578181}

# This is an automated release commit.
# Do not revert without consulting chrome-pmo@google.com.
NOAUTOREVERT=true
TBR=amineer@chromium.org

Change-Id: I851db72337e40a9496d9bb421bd7d1b4c8916a32
Reviewed-on: https://chromium-review.googlesource.com/1150890Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578180}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/ee658ba8..1e6d83a2

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: I2b4e30b5c9c7f5d83b62cf40064b51ea8c843325
Reviewed-on: https://chromium-review.googlesource.com/1150867Reviewed-by: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#578179}

The hit test "point" is not really a point, but a pixel with 1px width
and height. Ignoring this leads to off-by-one errors when converting
a physical point into logical in vertical-rl writing mode.

This patch fixes the issue by using 1px width and height in the
conversion, instead of 0.

Note: This patch contains an all-pass NG baseline because the legacy
baseline contains a failure line.

Bug: 811502
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ie3f01469b4902c3c9647d40be92ccb9c26467f0d
Reviewed-on: https://chromium-review.googlesource.com/1150814
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578178}

to prevent crash when enabling ARC IMEs.

Bug: 845079
Change-Id: If927b31d1ebb2d27ba4a50dc33a96ca6b4979a0d
Reviewed-on: https://chromium-review.googlesource.com/1150005Reviewed-by: Yusuke Sato <yusukes@chromium.org>
Commit-Queue: Yuichiro Hanada <yhanada@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578177}

This change moves it to a more generic name, RendererUpdater, in preparation for sending a few more pref updates. The only behavior change is to fix sending signin-notifications to renderers that share the same Profile as where the notification is coming from.

Bug: 841313
Change-Id: I3d408cca35cdc89e1fc0cf8d9b0a43c9e172e739
Reviewed-on: https://chromium-review.googlesource.com/1150825Reviewed-by: Jun Cai <juncai@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578176}

Extension might be uninstalled before install so the assoicated policies
are unregistered before registered. For example, a policy forced
extension is removed from forced list during launch due to policy update.

Remove the DCHECK for this situation because it does not break anything.

Bug: 864630, 734523
Change-Id: I71968c6930e3f72cd532c8a067e6019f0202300a
Reviewed-on: https://chromium-review.googlesource.com/1147469
Commit-Queue: Owen Min <zmin@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578175}

R=pwnall@chromium.org

Bug: 857464
Change-Id: I14a530854764fb07c875a5b1a19ce35359a662fb
Reviewed-on: https://chromium-review.googlesource.com/1150838Reviewed-by: Chase Phillips <cmp@chromium.org>
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578174}

Change-Id: Icf2ca10fcd3a04543b7ec28426678dbb9b437e83
Reviewed-on: https://chromium-review.googlesource.com/1149435Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Rob Schonberger <robsc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578173}

R=rch@chromium.org

Change-Id: I93d8c963e2d40a409aab5985625659e39f3ffb87
Reviewed-on: https://chromium-review.googlesource.com/1150883Reviewed-by: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Victor Vasiliev <vasilvv@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578172}

This is a reland of 61697367, which had
been reverted in 9a4096be as part of
reverting 568cc6a9 which had broken some
builders. That CL has now been fixed and relanded
(a9b7a993).

This reland is the same as the original.

Original change's description:
> MSE: Log when MP4 keyframe-ness mismatches the compressed media
>
> Logs to chrome://media-internals when the container's keyframe metadata
> for a frame mismatches the contents of that frame (if the latter was
> determined by the respective bitstream converter's Analyze()
> implementation, of whom only AVC currently does any keyframe analysis).
>
> BUG=860420,584384
> TEST=Repro crbug 860420 shows logs, new MP4StreamParserTest.AVC_Key* and media
>
> Change-Id: Ic87eab8726ad76b36b569df08ab2212b267008c2
> Reviewed-on: https://chromium-review.googlesource.com/1149153
> Reviewed-by: Dan Sanders <sandersd@chromium.org>
> Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#577751}

TBR=sandersd@chromium.org

Bug: 860420, 584384
Change-Id: I5a00819883e71ca9fd8c1a211956bdca66047b54
Reviewed-on: https://chromium-review.googlesource.com/1150541Reviewed-by: Matthew Wolenetz <wolenetz@chromium.org>
Reviewed-by: Dan Sanders <sandersd@chromium.org>
Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578171}

Make custom backgrounds accessible via screen readers, keyboard navigation,
and mouse navigation. For pure mouse-navigation hide all focus outlines.

To make this work properly keyboard navigation of the dialogs is treated as
the default. Opening a dialog with the mouse will force the UI into mouse-navigation,
hiding focus rings until the user attempts to navigate using the keyboard (tab or
arrow keys).

Change the tabstops to align with recommendations from the a11y team. Most
notably the entire tile container is now one tabstop and the individual tiles
can then be navigated using the arrow keys.

Bug: 858885
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I567552991777cd369fdfe456eda00a47383cf68f
Reviewed-on: https://chromium-review.googlesource.com/1141167
Commit-Queue: Kyle Milka <kmilka@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578170}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/01ce05914f99..ad463c9517e3


git log 01ce05914f99..ad463c9517e3 --date=short --no-merges --format='%ad %ae %s'
2018-07-25 ehmaldonado@chromium.org git-cl: Report known project urls.


Created with:
  gclient setdep -r src/third_party/depot_tools@ad463c9517e3

The AutoRoll server is located here: https://depot-tools-chromium-roll.skia.org

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.



BUG=chromium:832386
TBR=agable@chromium.org

Change-Id: I916e36750d4892c931a8be2a51a40a94d296c205
Reviewed-on: https://chromium-review.googlesource.com/1150055Reviewed-by: depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#578169}

Bug: 862744
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Ia4952bee3b44ccd9b9c3c564fab88dd5a7c18668
Reviewed-on: https://chromium-review.googlesource.com/1150904Reviewed-by: edchin <edchin@chromium.org>
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578168}

DevTools should initiate browser-side reload so that reload button doesn't
change behavior with and without devtools open.

R=dgozman

Bug: 817413
Change-Id: Ia69070c82e7ea46e165c485081ab2fe965fae531
Reviewed-on: https://chromium-review.googlesource.com/1107118
Commit-Queue: Andrey Lushnikov <lushnikov@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578167}

This reverts commit d6ec8154.

Reason for revert: Findit identified the culprit r577957 with confidence 100.0% in the config "chromium.mac / Mac10.11 Tests"

Original change's description:
> Enable FlingSchedulerMac
> 
> Enable tests that were disabled because of this functionality missing.
> 
> Bug: 842325
> Change-Id: I6f540460f4e5f81d7ff8dd36e4abf369f0bd4785
> Reviewed-on: https://chromium-review.googlesource.com/1149612
> Reviewed-by: Jonathan Ross <jonross@chromium.org>
> Commit-Queue: ccameron <ccameron@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#577957}

TBR=ccameron@chromium.org,jonross@chromium.org

Change-Id: I4a38151ba5333ca99fb28c00f57f93f057f5fd4b
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 842325, 867668
Reviewed-on: https://chromium-review.googlesource.com/1150946Reviewed-by: Yoichi Osato <yoichio@chromium.org>
Commit-Queue: Yoichi Osato <yoichio@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578166}

Bug: 865114
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Iaf96f48918f1a8556e3f7de94cc2f2470034245e
Reviewed-on: https://chromium-review.googlesource.com/1149663Reviewed-by: John Wu <jzw@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Reviewed-by: Hiroshi Ichikawa <ichikawa@chromium.org>
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Commit-Queue: Scott Wu <scottwu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578165}

https://chromium.googlesource.com/angle/angle.git/+log/eb4b86975848..203b26f27d00


git log eb4b86975848..203b26f27d00 --date=short --no-merges --format='%ad %ae %s'
2018-07-26 jiawei.shao@intel.com ES31: Translate compute shader HLSL system variables in compile time


Created with:
  gclient setdep -r src/third_party/angle@203b26f27d00

The AutoRoll server is located here: https://angle-chromium-roll.skia.org

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=geofflang@chromium.org

Change-Id: Ide4416326f1c07a364fa09c07a33f3e42cfaf77c
Reviewed-on: https://chromium-review.googlesource.com/1150370Reviewed-by: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#578164}

For overscrolling, we calculate the overlap between the virtual keyboard
and the window bounds of the render widget. This doesn't work for
webviews used as dialogs, as the window of a webview is the same as its
parent, which has a much larger size of the actual webview.

We change the overscrolling code to compute the overlap based on the
webview bounds rather than window bounds.

Bug: 865774
Change-Id: I26c4e87215c2c168a8dc827f6d6b6859fdb6268c
Reviewed-on: https://chromium-review.googlesource.com/1150012Reviewed-by: Yuichiro Hanada <yhanada@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578163}

ash::Shell is created in PreProfileInit() step and ArcImeService is
started in PostProfileInit() step, so it is safe to register
FocusObserver in the constructor of ArcImeService.
This CL also cleans up IsExoWindow() and IsArcWindow() in
ArcWindowDelegateImpl.

Bug: 866784
Test: browser_tests, components_unittests
Change-Id: I3bd32f4e888f86cbd215791e559901e1457694e2
Reviewed-on: https://chromium-review.googlesource.com/1148089
Commit-Queue: Yuichiro Hanada <yhanada@chromium.org>
Reviewed-by: Kazuhiro Inaba <kinaba@chromium.org>
Reviewed-by: Yusuke Sato <yusukes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578162}

RecentTabs was changed and it can now be opened from incognito,
for this reason we now need to update restoreTabWithSessionID
to make sure it always uses the non-incognito browserState.

Bug: 866854
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Ifc7147df943997a1f0784af926ac95cf9735fdaa
Reviewed-on: https://chromium-review.googlesource.com/1150579Reviewed-by: Kurt Horimoto <kkhorimoto@chromium.org>
Reviewed-by: edchin <edchin@chromium.org>
Commit-Queue: edchin <edchin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578161}

Dialog may be activated using ctrl+search+(d or m or h).
Previously when using the accelerators on the signin screen, the dialog
would be displayed after signing in.


Bug: 860093
Test: Manual
Change-Id: Idb8031d46951d80cd4f5dbcdb0af283b50bbb62d
Reviewed-on: https://chromium-review.googlesource.com/1144581
Commit-Queue: Sara Kato <sarakato@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578160}

If ArcInputMethodManagerService fails to switch active IME in Android
, active IME in Chrome OS should be switched to previous active IME
automatically.

Bug: 845079
Change-Id: Ibcdaf14db66459557c2bd0738d04d8ac44f0aa76
Reviewed-on: https://chromium-review.googlesource.com/1148308
Commit-Queue: Yuichiro Hanada <yhanada@chromium.org>
Reviewed-by: Yusuke Sato <yusukes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578159}

https://pdfium.googlesource.com/pdfium.git/+log/a5d2bf1131fe..91b8302dec04


git log a5d2bf1131fe..91b8302dec04 --date=short --no-merges --format='%ad %ae %s'
2018-07-25 tsepez@chromium.org Use incomplete type CFX_BmpContext in place of void*
2018-07-25 thestig@chromium.org Change GetHeaderOffset() to return Optional<FX_FILESIZE>.
2018-07-25 hnakashima@chromium.org Create popup with Contents only for same annotations subtypes.


Created with:
  gclient setdep -r src/third_party/pdfium@91b8302dec04

The AutoRoll server is located here: https://pdfium-roll.skia.org

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

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.



BUG=chromium:856331
TBR=dsinclair@chromium.org

Change-Id: I057ec93d3344dec364419351204f575254990b25
Reviewed-on: https://chromium-review.googlesource.com/1150368Reviewed-by: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#578158}