commit b7270e498fe200e9b25a9db5ba00b245741185bb 70.0.3538.69 author chrome-release-bot <chrome-release-bot@chromium.org> Wed Oct 17 00:10:21 2018 committer chrome-release-bot <chrome-release-bot@chromium.org> Wed Oct 17 00:10:21 2018 Publish DEPS for 70.0.3538.69 DEPS diff]

commit 49b19fa81cd9ac65c8f1ce0135c476d871d7177a author chrome-release-bot <chrome-release-bot@chromium.org> Wed Oct 17 00:08:48 2018 committer chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Wed Oct 17 00:08:48 2018 Incrementing VERSION to 70.0.3538.69 TBR=amineer@chromium.org Change-Id: I5427310cda03a8c12d5f57099c3dbcf57dba6ab1 Reviewed-on: https://chromium-review.googlesource.com/c/1285629 Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#1008} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/VERSION diff]

commit 48b21aa6c189e2d73965efcd250e9b722a9671ac author Tetsui Ohkubo <tetsui@chromium.org> Tue Oct 16 06:25:05 2018 committer Tetsui Ohkubo <tetsui@chromium.org> Tue Oct 16 06:25:05 2018 Reland "Fix MessageListView crash on update during close." This is a reland of f89130423e81cec991faaafe8e72ef395551c271 Original change's description: > Fix MessageListView crash on update during close. > > MessageListView crashes when a notification is updated during the > UnifiedSystemTray is closing. Like other views::Widget methods, > SynthesizeMouseMoveEvent() should not be called during the widget is > closing. > > See the bug for the asan trace. > > TEST=manual > BUG=894070 > TBR=tetsui@chromium.org > > (cherry picked from commit 987d8bc9ecb65c60f8ebec3527546e9a9d35d2ca) > > Change-Id: I9ffba0f73260542ebf21b2aef572af1f68e5c40b > Reviewed-on: https://chromium-review.googlesource.com/c/1276225 > Commit-Queue: James Cook <jamescook@chromium.org> > Reviewed-by: James Cook <jamescook@chromium.org> > Cr-Original-Commit-Position: refs/heads/master@{#598768} > Reviewed-on: https://chromium-review.googlesource.com/c/1278615 > Reviewed-by: Tetsui Ohkubo <tetsui@chromium.org> > Cr-Commit-Position: refs/branch-heads/3538@{#993} > Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} Bug: 894070 Change-Id: I6143d002102b0bf4d21bc658a1301c9c4a08fd69 Reviewed-on: https://chromium-review.googlesource.com/c/1282487 Reviewed-by: Tetsui Ohkubo <tetsui@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#1007} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} ash/message_center/message_list_view.cc diff]

commit 287d2063d96c9d78a8143f386f0cbadcaa8a1736 author Tetsui Ohkubo <tetsui@chromium.org> Tue Oct 16 06:12:31 2018 committer Tetsui Ohkubo <tetsui@chromium.org> Tue Oct 16 06:12:31 2018 Revert "Fix MessageListView crash on update during close." This reverts commit f89130423e81cec991faaafe8e72ef395551c271. Reason for revert: Incomplete fix Original change's description: > Fix MessageListView crash on update during close. > > MessageListView crashes when a notification is updated during the > UnifiedSystemTray is closing. Like other views::Widget methods, > SynthesizeMouseMoveEvent() should not be called during the widget is > closing. > > See the bug for the asan trace. > > TEST=manual > BUG=894070 > TBR=tetsui@chromium.org > > (cherry picked from commit 987d8bc9ecb65c60f8ebec3527546e9a9d35d2ca) > > Change-Id: I9ffba0f73260542ebf21b2aef572af1f68e5c40b > Reviewed-on: https://chromium-review.googlesource.com/c/1276225 > Commit-Queue: James Cook <jamescook@chromium.org> > Reviewed-by: James Cook <jamescook@chromium.org> > Cr-Original-Commit-Position: refs/heads/master@{#598768} > Reviewed-on: https://chromium-review.googlesource.com/c/1278615 > Reviewed-by: Tetsui Ohkubo <tetsui@chromium.org> > Cr-Commit-Position: refs/branch-heads/3538@{#993} > Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} TBR=jamescook@chromium.org,tetsui@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 894070 Change-Id: I465f935b57e5c9aa2375bf190e28cdef29dae1a8 Reviewed-on: https://chromium-review.googlesource.com/c/1282486 Reviewed-by: Tetsui Ohkubo <tetsui@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#1006} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} ash/message_center/message_list_view.cc diff]

commit 95153532e0956eff61017e0b5c66dcf392f7626c author chrome-release-bot <chrome-release-bot@chromium.org> Tue Oct 16 00:10:43 2018 committer chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Tue Oct 16 00:10:43 2018 Incrementing VERSION to 70.0.3538.68 TBR=govind@chromium.org Change-Id: Idd3ee50b6394f033ad9e13b8ba97a86eee24824b Reviewed-on: https://chromium-review.googlesource.com/c/1282282 Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#1005} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/VERSION diff]

commit 8d0c105144240f56de7c48a9ca9bf2c86a47fd02 author Luciano Pacheco <lucmult@chromium.org> Mon Oct 15 23:28:18 2018 committer Luciano Pacheco <lucmult@chromium.org> Mon Oct 15 23:28:18 2018 Fix naming issue when renaming files inside My files Change DirectoryModel to "unwrap" VolumeEntry when it's selected via file list. This fixes the issue where after selecting a VolumeEntry any operation in the private API would fail because it wouldn't be able to send a VolumeEntry to private API, because it requires a real Entry. This fixes the user issue of trying to rename and always getting "Use shorter name" error, even with a short name. Update FakeEntry to be an implementation of FilesAppDirEntry, since all users were using as directory, also update some functions to typing to use FilesAppDirEntry instead of FakeEntry which is more correct. Manually merged on M70 branch. Test: browser_tests --gtest_filter="*/myFilesFolderRename" Bug: 889636 Change-Id: Ieb75ffbb811a91e4742fb7a49a3badfd129376ad Reviewed-on: https://chromium-review.googlesource.com/c/1276067 Reviewed-by: Joel Hockey <joelhockey@chromium.org> Commit-Queue: Luciano Pacheco <lucmult@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#599136} Reviewed-on: https://chromium-review.googlesource.com/c/1282142 Reviewed-by: Luciano Pacheco <lucmult@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#1004} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/chromeos/file_manager/file_manager_browsertest.cc diff]

ui/file_manager/file_manager/background/js/mock_volume_manager.js diff]

ui/file_manager/file_manager/background/js/volume_info_impl.js diff]

ui/file_manager/file_manager/background/js/volume_manager_impl.js diff]

ui/file_manager/file_manager/common/js/files_app_entry_types.js diff]

ui/file_manager/file_manager/common/js/files_app_entry_types_unittest.js diff]

ui/file_manager/file_manager/common/js/util.js diff]

ui/file_manager/file_manager/common/js/volume_manager_common.js diff]

ui/file_manager/file_manager/foreground/js/directory_model.js diff]

ui/file_manager/file_manager/foreground/js/file_manager.js diff]

ui/file_manager/file_manager/foreground/js/file_transfer_controller.js diff]

ui/file_manager/file_manager/foreground/js/file_watcher.js diff]

ui/file_manager/file_manager/foreground/js/navigation_list_model.js diff]

ui/file_manager/integration_tests/file_manager/my_files.js diff]

commit d26b21fb177c26f7eb7f9d3294ef2c9172cda75f author Henrique Grandinetti <hgrandinetti@chromium.org> Mon Oct 15 22:36:09 2018 committer Aga Wronska <agawronska@chromium.org> Mon Oct 15 22:36:09 2018 Store remaining usage time in milliseconds It was stored in minutes, which was causing some rounding problems when the CheckTimeLimit function was called less than 1 minute before the device being locked by a screen time. Bug: 895036 Change-Id: Ia6d243e8d59e32fa07151e76542b6235caf5b33a Reviewed-on: https://chromium-review.googlesource.com/c/1281662 Commit-Queue: Henrique Grandinetti <hgrandinetti@google.com> Commit-Queue: Rahul Chaturvedi <rkc@chromium.org> Reviewed-by: Rahul Chaturvedi <rkc@chromium.org> Reviewed-by: Aga Wronska <agawronska@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#599747}(cherry picked from commit 085ecdf2a18350a1964a65ef5b48a663ae7228ec) Reviewed-on: https://chromium-review.googlesource.com/c/1281724 Cr-Commit-Position: refs/branch-heads/3538@{#1003} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/chromeos/child_accounts/screen_time_controller.cc diff]

commit 9ab0cfab84ded083718d3a4ff830726efd38869f author chrome-release-bot <chrome-release-bot@chromium.org> Mon Oct 15 20:07:27 2018 committer chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Mon Oct 15 20:07:27 2018 Incrementing VERSION to 70.0.3538.67 TBR=amineer@chromium.org Change-Id: I15452a585dbb3baa72c19820b12e0b2b216a1ed0 Reviewed-on: https://chromium-review.googlesource.com/c/1281583 Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#1002} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/VERSION diff]

commit f76dbb3f565d512a252a36748e860a5e3f4c5bff author Henrique Grandinetti <hgrandinetti@chromium.org> Mon Oct 15 18:24:32 2018 committer Aga Wronska <agawronska@chromium.org> Mon Oct 15 18:24:32 2018 Fix UsageTimeLimitProcessor to handle state properly when usage time limit takes effect immediately. Bug: 895036 Change-Id: Icfa7364e8217e4df9904154bf1372328187bd4a6 Reviewed-on: https://chromium-review.googlesource.com/c/1279368 Reviewed-by: Aga Wronska <agawronska@chromium.org> Reviewed-by: Rahul Chaturvedi <rkc@chromium.org> Commit-Queue: Henrique Grandinetti <hgrandinetti@google.com> Cr-Original-Commit-Position: refs/heads/master@{#599467}(cherry picked from commit dbe0d3e4b99d5884ff5231fc45412661a4421fea) Reviewed-on: https://chromium-review.googlesource.com/c/1280644 Cr-Commit-Position: refs/branch-heads/3538@{#1001} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/chromeos/child_accounts/usage_time_limit_processor.cc diff]

commit 728442c62bcd804b075b03e13e824fe1bd3bab37 author Xianzhu Wang <wangxianzhu@chromium.org> Mon Oct 15 18:01:57 2018 committer Xianzhu Wang <wangxianzhu@chromium.org> Mon Oct 15 18:01:57 2018 [PE] Don't paint outline on foreground layer "Background" of the foreground layer: A foreground layer is created for a composited scrolling element with composited negative-z-order descendants. It's actually another scrolling contents layer which paints non-composited normal and positive-z-order descendants, while the original scrolling contents layer paints the scrolling background and descendants below the composited negative-z-order layer. The foreground layer and the scrolling contents layer both scroll and use the contents property tree state. Previously we mistakenly painted outline on the foreground layer (and on the main layer). The bug had existed before SPv175 when we could see an extra outline scrolling with the contents. In SPv175, we saw an error message saying that the outline's chunk's clip state escaped the layer's clip state, and the foreground layer was fully raster invalidated on each scroll. Not sure how the clip-escaping broke rendering. TBR=wangxianzhu@chromium.org (cherry picked from commit 89879ac0cab5651b77aa9dd512f9544dc7454b63) Bug: 886997,892855 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I9ad7db2baa526f085676f13c429460c4ff46322c Reviewed-on: https://chromium-review.googlesource.com/c/1278990 Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#599412} Reviewed-on: https://chromium-review.googlesource.com/c/1280929 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#1000} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} third_party/WebKit/LayoutTests/flag-specific/enable-slimming-paint-v2/paint/invalidation/compositing/should-not-paint-outline-on-foreground-layer-expected.txt [Added - diff

third_party/WebKit/LayoutTests/paint/invalidation/compositing/should-not-paint-outline-on-foreground-layer-expected.html [Added - diff

third_party/WebKit/LayoutTests/paint/invalidation/compositing/should-not-paint-outline-on-foreground-layer-expected.txt [Added - diff

third_party/WebKit/LayoutTests/paint/invalidation/compositing/should-not-paint-outline-on-foreground-layer.html [Added - diff

third_party/blink/renderer/core/paint/paint_layer_painter.cc diff]

commit 11b6e1514b81e3ad1524262d5d56ef98b29f4527 author Mihai Sardarescu <msarda@google.com> Mon Oct 15 15:41:44 2018 committer Mihai Sardarescu <msarda@chromium.org> Mon Oct 15 15:41:44 2018 Do not start a sign-in flow when browser sign-in is disallowed. This CL returns errors to all extensions that attempt to start a sign-in flow via the chrome.identity API if browser sign-in is not allowed. Bug: 894071 Change-Id: I38d25e551a89ba9dfdd8c4e67f935611acc95a70 Reviewed-on: https://chromium-review.googlesource.com/c/1273645 Commit-Queue: Mihai Sardarescu <msarda@chromium.org> Reviewed-by: David Roger <droger@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598490}(cherry picked from commit fb977abb942751a4bfa938e212448899574da0ac) Reviewed-on: https://chromium-review.googlesource.com/c/1280432 Reviewed-by: Mihai Sardarescu <msarda@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#999} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/extensions/api/identity/identity_apitest.cc diff]

chrome/browser/extensions/api/identity/identity_constants.cc diff]

chrome/browser/extensions/api/identity/identity_constants.h diff]

chrome/browser/extensions/api/identity/identity_get_auth_token_function.cc diff]

commit db54921dea346d5d2676be91eba718a311916db1 author Ben Smith <binji@chromium.org> Mon Oct 15 15:22:07 2018 committer Ben Smith <binji@chromium.org> Mon Oct 15 15:22:07 2018 Allow posting a SharedArrayBuffer to AudioWorklet The HTML spec only allows passing SharedArrayBuffers to an agent in the same agent cluster. Worklets currently do not belong to any agent cluster, so a SharedArrayBuffer can not be shared with a worklet. However, it is intended that this is possible; see, for example, https://github.com/w3c/css-houdini-drafts/issues/380 and the AudioWorklet article here: https://developers.google.com/web/updates/2018/06/audio-worklet-design-pattern#webaudio_powerhouse_audio_worklet_and_sharedarraybuffer This change funnels the agent cluster ID through when creating a ThreadedWorklet, so a SharedArrayBuffer can be shared as long as the creator of the Worklet's thread is in the same agent cluster. It is not clear that this is the behavior that will be specified, however. Bug: chromium:892067 Change-Id: If1a2187ae38da41f2389538c07e7b04921c6128f Reviewed-on: https://chromium-review.googlesource.com/c/1262932 Commit-Queue: Ben Smith <binji@chromium.org> Reviewed-by: Hongchan Choi <hongchan@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598619}(cherry picked from commit 97167bddb398b0adb7e06f6f5c68e9f5d556ad96) Reviewed-on: https://chromium-review.googlesource.com/c/1280843 Reviewed-by: Ben Smith <binji@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#998} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} third_party/WebKit/LayoutTests/external/wpt/webaudio/the-audio-api/the-audioworklet-interface/audioworklet-postmessage-sharedarraybuffer.https.html [Added - diff

third_party/WebKit/LayoutTests/external/wpt/webaudio/the-audio-api/the-audioworklet-interface/processors/sharedarraybuffer-processor.js [Added - diff

third_party/blink/renderer/core/workers/threaded_worklet_messaging_proxy.cc diff]

third_party/blink/renderer/core/workers/worklet_global_scope.cc diff]

third_party/blink/renderer/core/workers/worklet_global_scope.h diff]

commit f7542c2e3942eeec520bacd531ed181c98773676 author Yoshifumi Inoue <yosin@chromium.org> Mon Oct 15 02:23:39 2018 committer Yoshifumi Inoue <yosin@chromium.org> Mon Oct 15 02:23:39 2018 Make ReplaceSelectionCommand::CompleteHTMLReplacement() not to use out-of-bound position This patch changes |ReplaceSelectionCommand::CompleteHTMLReplacement()| not to use out-of-bound position to proper execution and avoid to hit DCHECK() in |Position| constructor. This issue is cause by positions hold in local variable |start| and |end| can be out-of-position by |ApplyStyle()| since it split |Text| node which is anchor node of |start| and |end|. Bug: 877127 Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng Change-Id: I564bbe953ab7660e099b193cb5b59e68d6454e8f Reviewed-on: https://chromium-review.googlesource.com/c/1260126 Commit-Queue: Yoshifumi Inoue <yosin@chromium.org> Reviewed-by: Yoichi Osato <yoichio@chromium.org> Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#597866}(cherry picked from commit dda816d236f796571ef338fb380399baaddd9dd1) Reviewed-on: https://chromium-review.googlesource.com/c/1278641 Reviewed-by: Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#997} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} third_party/blink/renderer/core/editing/commands/replace_selection_command.cc diff]

third_party/blink/renderer/core/editing/commands/replace_selection_command_test.cc diff]

commit 7167e3789463142cd3dd49489d1f0bd219db8b70 author chrome-release-bot <chrome-release-bot@chromium.org> Mon Oct 15 00:07:40 2018 committer chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Mon Oct 15 00:07:40 2018 Incrementing VERSION to 70.0.3538.66 TBR=mmoss@chromium.org Change-Id: If3901806a8881ebe1ae468d4d277f75fac853a82 Reviewed-on: https://chromium-review.googlesource.com/c/1280042 Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#996} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/VERSION diff]

commit 33c0f34ef8e2ba25f65078ca1cca21f70e4c8ab8 author David Gunnarsson <dgunnarsson@vewd.com> Sun Oct 14 13:20:38 2018 committer David Tseng <dtseng@chromium.org> Sun Oct 14 13:20:38 2018 Merge to m70: Fix nullpointer crash when traversing accessibility tree TBR=dmazzoni@chromium.org Bug: 888566 Change-Id: I2a067705707646f3a2021fb7107661a2c4745bd5 Reviewed-on: https://chromium-review.googlesource.com/1243283 Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#593974}(cherry picked from commit 210142632c6eb24d66dbd4e9a675645a4022839f) Reviewed-on: https://chromium-review.googlesource.com/c/1279955 Reviewed-by: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#995} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/renderer/extensions/automation_internal_custom_bindings.cc diff]

commit b13349d1145e6116ec206c7456faad241f92b744 author chrome-release-bot <chrome-release-bot@chromium.org> Sun Oct 14 00:09:30 2018 committer chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Sun Oct 14 00:09:30 2018 Incrementing VERSION to 70.0.3538.65 TBR=govind@chromium.org Change-Id: Ifaf5688c62d74b9619dc0f96e527b05fc8541d40 Reviewed-on: https://chromium-review.googlesource.com/c/1278909 Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#994} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/VERSION diff]

commit f89130423e81cec991faaafe8e72ef395551c271 author Tetsui Ohkubo <tetsui@chromium.org> Sat Oct 13 07:12:13 2018 committer Tetsui Ohkubo <tetsui@chromium.org> Sat Oct 13 07:12:13 2018 Fix MessageListView crash on update during close. MessageListView crashes when a notification is updated during the UnifiedSystemTray is closing. Like other views::Widget methods, SynthesizeMouseMoveEvent() should not be called during the widget is closing. See the bug for the asan trace. TEST=manual BUG=894070 TBR=tetsui@chromium.org (cherry picked from commit 987d8bc9ecb65c60f8ebec3527546e9a9d35d2ca) Change-Id: I9ffba0f73260542ebf21b2aef572af1f68e5c40b Reviewed-on: https://chromium-review.googlesource.com/c/1276225 Commit-Queue: James Cook <jamescook@chromium.org> Reviewed-by: James Cook <jamescook@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598768} Reviewed-on: https://chromium-review.googlesource.com/c/1278615 Reviewed-by: Tetsui Ohkubo <tetsui@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#993} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} ash/message_center/message_list_view.cc diff]

commit 85ae797816dcf3e8b4697ede78a60dce5d63475d author chrome-release-bot <chrome-release-bot@chromium.org> Sat Oct 13 00:09:34 2018 committer chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Sat Oct 13 00:09:34 2018 Incrementing VERSION to 70.0.3538.64 TBR=amineer@chromium.org Change-Id: I0afed9f5f8b0cd9713514fea03dcec99d0fb97cf Reviewed-on: https://chromium-review.googlesource.com/c/1279367 Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#992} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/VERSION diff]

commit c97a2f31c8ee1e14d988cd18a9b32a0260acf63a author Yue Li <updowndota@chromium.org> Fri Oct 12 23:02:24 2018 committer Yue Li <updowndota@chromium.org> Fri Oct 12 23:02:24 2018 Use SignInManager to get AccountInfo in first run There seems to be a regression on M70 head that get AccountInfo using identity_manager->GetPrimaryAccountInfo() always return empty hosted_domain field. Using signin_manager->GetAuthenticatedAccountInfo() seems to be a more stable way. Bug: b/116746192 Test: Local build Change-Id: I8369787b4f8d33e63d4029705d9f3f02c1a0376d Reviewed-on: https://chromium-review.googlesource.com/c/1278526 Reviewed-by: Xiyuan Xia <xiyuan@chromium.org> Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org> Commit-Queue: Yue Li <updowndota@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#599348}(cherry picked from commit 48cafafc916b343af2d63f148e34df1b233b6c47) Reviewed-on: https://chromium-review.googlesource.com/c/1279291 Reviewed-by: Yue Li <updowndota@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#991} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/chromeos/first_run/first_run.cc diff]

commit 4c77f77c82ed718b2e9163a4a7c99c0554e2b466 author Chris Harrelson <chrishtr@chromium.org> Fri Oct 12 23:01:03 2018 committer Chris Harrelson <chrishtr@chromium.org> Fri Oct 12 23:01:03 2018 Set dirty bits for GraphicsLayerUpdater correctly for PaintLayers that are squashed. Previously, a PaintLayer whose compositing inputs changed didn't propagate those changes to the squashing layer, if the PaintLayer was squashed. Bug: 890638 TBR=chrishtr@chromium.org (cherry picked from commit 2bd342fdf320e2e38bc48ef3a71355c8815b2b21) Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I0ad3bb79aa15e59eca9efd443f40cd5b66dcd583 Reviewed-on: https://chromium-review.googlesource.com/c/1274895 Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: vmpstr <vmpstr@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598894} Reviewed-on: https://chromium-review.googlesource.com/c/1279346 Reviewed-by: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#990} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} third_party/WebKit/LayoutTests/compositing/squashing/overflow-change-squash-non-ancestor-expected.html [Added - diff

third_party/WebKit/LayoutTests/compositing/squashing/overflow-change-squash-non-ancestor.html [Added - diff

third_party/blink/renderer/core/paint/compositing/compositing_inputs_updater.cc diff]

third_party/blink/renderer/core/paint/compositing/compositing_inputs_updater.h diff]

commit 89607f31840ab9859cecfc44e937b3b238ce383e author Krishna Govind <govind@chromium.org> Fri Oct 12 22:36:40 2018 committer Krishna Govind <govind@chromium.org> Fri Oct 12 22:36:40 2018 Updating XTBs based on .GRDs from branch 3538 R=cmasso@chromium.org Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs Change-Id: Ia102b647194d2eb4a9c3c6c2fe434fbbdb889e34 Reviewed-on: https://chromium-review.googlesource.com/c/1279238 Reviewed-by: Krishna Govind <govind@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#989} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} ash/components/strings/ash_components_strings_te.xtb diff]

ash/strings/ash_strings_te.xtb diff]

chrome/app/resources/chromium_strings_te.xtb diff]

chrome/app/resources/generated_resources_gu.xtb diff]

chrome/app/resources/generated_resources_hi.xtb diff]

chrome/app/resources/generated_resources_kn.xtb diff]

chrome/app/resources/generated_resources_no.xtb diff]

chrome/app/resources/generated_resources_te.xtb diff]

chrome/app/resources/generated_resources_zh-CN.xtb diff]

chrome/app/resources/google_chrome_strings_te.xtb diff]

chrome/browser/resources/chromeos/chromevox/strings/chromevox_strings_te.xtb diff]

components/policy/resources/policy_templates_no.xtb diff]

components/policy/resources/policy_templates_te.xtb diff]

components/strings/components_strings_te.xtb diff]

ios/chrome/app/strings/resources/ios_chromium_strings_te.xtb diff]

ios/chrome/app/strings/resources/ios_google_chrome_strings_te.xtb diff]

ios/chrome/app/strings/resources/ios_strings_te.xtb diff]

remoting/resources/remoting_strings_te.xtb diff]

ui/accessibility/extensions/strings/accessibility_extensions_strings_te.xtb diff]

commit 2f179eaa22bc4c40bb438eba31ffe2be210206d8 author Christopher Cameron <ccameron@chromium.org> Fri Oct 12 20:20:31 2018 committer ccameron <ccameron@chromium.org> Fri Oct 12 20:20:31 2018 Mac: Blacklist all GPU features for GL <4.1 This is a very small set of machines, which have been exhibiting - rendering artifacts when GPU compositing is enabled - severe rendering artifacts when GPU raster is enabled TBR=ccameron@chromium.org (cherry picked from commit a361a69018d5b46ba3a29f7818e717451a92a09f) Bug: 875891 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 Change-Id: Ie49a9111b9723977a2b8758f824bba7843238d32 Reviewed-on: https://chromium-review.googlesource.com/1220180 Reviewed-by: ccameron <ccameron@chromium.org> Reviewed-by: Kenneth Russell <kbr@chromium.org> Reviewed-by: Zhenyao Mo <zmo@chromium.org> Commit-Queue: ccameron <ccameron@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#590516} Reviewed-on: https://chromium-review.googlesource.com/c/1277584 Cr-Commit-Position: refs/branch-heads/3538@{#988} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} gpu/config/software_rendering_list.json diff]

commit 1a23bc792513bc03c09c4366383c101bd196b727 author Dale Curtis <dalecurtis@chromium.org> Fri Oct 12 19:57:54 2018 committer Dale Curtis <dalecurtis@chromium.org> Fri Oct 12 19:57:54 2018 Merge M70: "Ensure we actually toss all MediaCodec indices after flush()." Depending on which process the MediaCodec is running in, there may already be a non-default looper and handler which results in stale input/output indexes being delivered to the bridge after start(). To prevent this, we now call start() immediately after flush(), but post the clearing of mPendingStart through the handler/looper. A sequence counter is added so that rapid flush()/stop() calls don't prematurely use invalid indices. BUG=892591 TEST=Run chrome with --in-process-gpu and seek a bunch on any video. Change-Id: I8c60a73b8c00c85a7ab3d253bc8df2397c1fa00d Reviewed-on: https://chromium-review.googlesource.com/c/1278293 Reviewed-by: Frank Liberato <liberato@chromium.org> Commit-Queue: Dale Curtis <dalecurtis@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#599283}(cherry picked from commit 15087953f0a74078f141271898fd8c71500a7ca5) Reviewed-on: https://chromium-review.googlesource.com/c/1279154 Reviewed-by: Dale Curtis <dalecurtis@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#987} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} media/base/android/java/src/org/chromium/media/MediaCodecBridge.java diff]

commit 37f31e2f5afdcaac82f2a024344bed87f8008aa9 author Will Harris <wfh@chromium.org> Fri Oct 12 19:44:21 2018 committer Will Harris <wfh@chromium.org> Fri Oct 12 19:44:21 2018 Branch M70: Update Flash plugin metadata versions to latest version. https://helpx.adobe.com/security/products/flash-player/apsb18-35.html This is a manual merge of https://chromium-review.googlesource.com/c/1278930 original git rev: c1f6f33f215868c9cd0f869d8a44b5a602812872 BUG=412078 TBR=jschuh@chromium.org Change-Id: I5c8ca494948d39f59ba68c0b3e5305850a148591 Reviewed-on: https://chromium-review.googlesource.com/c/1279152 Reviewed-by: Will Harris <wfh@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#986} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/resources/plugin_metadata/plugins_linux.json diff]

chrome/browser/resources/plugin_metadata/plugins_mac.json diff]

chrome/browser/resources/plugin_metadata/plugins_win.json diff]

commit 94c7e787eac52581d0142d7ebb0fe11a94d81c83 author Clark DuVall <cduvall@chromium.org> Fri Oct 12 19:29:04 2018 committer Clark DuVall <cduvall@chromium.org> Fri Oct 12 19:29:04 2018 Add about: handler for redirects in network service This is used by some extensions to redirect to using webrequest. This matches the behavior of URLRequestAboutJob. Bug: 894480 Change-Id: I565bb1072a657d1135273f14b1b91822033124de Reviewed-on: https://chromium-review.googlesource.com/c/1277265 Reviewed-by: John Abd-El-Malek <jam@chromium.org> Reviewed-by: Nasko Oskov <nasko@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598970}(cherry picked from commit e55815861b7a73781b2c68bdc849d6e2d656255c) Reviewed-on: https://chromium-review.googlesource.com/c/1277694 Reviewed-by: Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#985} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/test/data/extensions/api_test/webrequest/test_redirects.js diff]

content/browser/loader/loader_browsertest.cc diff]

content/browser/loader/navigation_url_loader_impl.cc diff]

commit a425c91521e7ecbdd405a066eeb623cd9ae3f0e1 author Alexander Alekseev <alemate@chromium.org> Fri Oct 12 18:31:23 2018 committer Alexander Alekseev <alemate@chromium.org> Fri Oct 12 18:31:23 2018 Chrome OS Sign-in screen: fix bottom-buttons overlay. This Cl ensures that Gaia screen gray button overlay actually covers not only buttons background, but all the buttons TBR=alemate@chromium.org (cherry picked from commit 2beab727d4449ec3bb797090e70a0f9dc8541cc1) Bug: 864290 Change-Id: I1990bb857ee974d8e93dcf893a8a2c9cd027c937 Reviewed-on: https://chromium-review.googlesource.com/c/1275265 Reviewed-by: Wenzhao (Colin) Zang <wzang@chromium.org> Commit-Queue: Alexander Alekseev <alemate@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598633} Reviewed-on: https://chromium-review.googlesource.com/c/1278798 Reviewed-by: Alexander Alekseev <alemate@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#984} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/resources/chromeos/login/oobe_dialog.css diff]

chrome/browser/resources/chromeos/login/oobe_dialog.html diff]

chrome/browser/resources/chromeos/login/oobe_dialog.js diff]

chrome/browser/resources/chromeos/login/screen_gaia_signin.css diff]

chrome/browser/resources/chromeos/login/screen_gaia_signin.html diff]

chrome/browser/resources/chromeos/login/screen_gaia_signin.js diff]

commit c61ca3c11f29762d87c1054568b219e0a0983427 author wutao <wutao@chromium.org> Fri Oct 12 18:06:26 2018 committer Tao Wu <wutao@chromium.org> Fri Oct 12 18:06:26 2018 [M70 merge] app_list: Fix callbacks in InternalAppResult This cl fixes a bug that |large_icon_service_| could outlive the InternalAppResult. Use WeakPtr in the callbacks. TBR=xiyuan@chromium.org Bug: 894595 Test: manual. Change-Id: Icac0c14611a631bbf62f3f2a0a205c174980a146 Reviewed-on: https://chromium-review.googlesource.com/c/1278130 Reviewed-by: Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Tao Wu <wutao@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598969}(cherry picked from commit 5637af2cbc5c634fea722f0cff0cb424ec9bf783) Reviewed-on: https://chromium-review.googlesource.com/c/1278951 Reviewed-by: Tao Wu <wutao@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#983} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/ui/app_list/search/internal_app_result.cc diff]

chrome/browser/ui/app_list/search/internal_app_result.h diff]

commit 83ad81a1ad7113b223d10ab10ec46bececfe0652 author John Budorick <jbudorick@chromium.org> Fri Oct 12 17:05:53 2018 committer John Budorick <jbudorick@chromium.org> Fri Oct 12 17:05:53 2018 3538: ios: fix earl grey DEPS hash. Bug: 888400 Change-Id: I7a6095dda1c10009b5649338439b09b0c9433d5f Reviewed-on: https://chromium-review.googlesource.com/1240177 Commit-Queue: John Budorick <jbudorick@chromium.org> Reviewed-by: John Budorick <jbudorick@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#593525}(cherry picked from commit 94d5eeb6cff7a9262c1c491076b7f7bf5105ced0) Reviewed-on: https://chromium-review.googlesource.com/c/1278538 Reviewed-by: Michael Moss <mmoss@chromium.org> Reviewed-by: Kariah Davis <kariahda@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#982} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} DEPS diff]

commit b8e57473c61d919743920f086344cec94c856f1c author Thomas Tangl <tangltom@chromium.org> Fri Oct 12 12:43:24 2018 committer Thomas Tangl <tangltom@chromium.org> Fri Oct 12 12:43:24 2018 [signin] Disable signin-allowed toggle for sync users When the user is signed in and syncing, the signin-allowed toggle is now disabled. Note: This CL is adapted from crrev.com/c/1273517 and removes the hint, i.e. there are no string changes here. Bug: 892745 Change-Id: I1778115390518860fca4b4f11588d5ca7c7b9210 Reviewed-on: https://chromium-review.googlesource.com/c/1275849 Reviewed-by: Jochen Eisinger <jochen@chromium.org> Commit-Queue: Thomas Tangl <tangltom@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598901}(cherry picked from commit 2f696e77df78a51eff611f3b8983fbe361a54f85) Reviewed-on: https://chromium-review.googlesource.com/c/1278169 Reviewed-by: Thomas Tangl <tangltom@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#981} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/resources/settings/privacy_page/BUILD.gn diff]

chrome/browser/resources/settings/privacy_page/privacy_page.html diff]

chrome/browser/resources/settings/privacy_page/privacy_page.js diff]

chrome/test/data/webui/settings/privacy_page_test.js diff]

commit 2ee0bde223709e41cdf700b1156ec69a9f8b8d13 author Ivan Sandrk <isandrk@google.com> Fri Oct 12 07:03:53 2018 committer Ivan Šandrk <isandrk@chromium.org> Fri Oct 12 07:03:53 2018 [M70][Locked Fullscreen] Fix Mac compilation TBR=isandrk@chromium.org Bug: 894702 Change-Id: I3b2810f60590a288acec355f1d381de3a9e6037a Reviewed-on: https://chromium-review.googlesource.com/c/1278627 Reviewed-by: Ivan Šandrk <isandrk@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#980} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/ui/cocoa/browser/exclusive_access_controller_views.h diff]

chrome/browser/ui/cocoa/browser/exclusive_access_controller_views.mm diff]

commit a1129f770400aee103259778a299d0d332222ff5 author chrome-release-bot <chrome-release-bot@chromium.org> Fri Oct 12 00:38:45 2018 committer chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Fri Oct 12 00:38:45 2018 Incrementing VERSION to 70.0.3538.63 TBR=mmoss@chromium.org Change-Id: I56cf55da07be99452a1aa05c9e39114ea2aaef82 Reviewed-on: https://chromium-review.googlesource.com/c/1278327 Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#979} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/VERSION diff]

commit e52c522051d6967cbb98a9f8874df3a4f1bf6850 author khmel@chromium.org <khmel@chromium.org> Fri Oct 12 00:27:00 2018 committer Yury Khmel <khmel@chromium.org> Fri Oct 12 00:27:00 2018 [Merge M70] arc: Support loading default apps from different sources. This is to support per-board configuration for uni-builds. Related CLs: crrev.com/c/1208892, crrev.com/i/673295 TEST=Manually on device, test data restructured to be covered by unit tests BUG=b:113908266 TBR=khmel@google.com (cherry picked from commit 5b56f9b244736a77295fb360827b3247db23b216) Change-Id: I56b3268390ce31e28204e53d443d465a032a84f4 Reviewed-on: https://chromium-review.googlesource.com/1208195 Commit-Queue: Yury Khmel <khmel@google.com> Reviewed-by: Xiyuan Xia <xiyuan@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#589395} Reviewed-on: https://chromium-review.googlesource.com/c/1238826 Reviewed-by: Yury Khmel <khmel@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#978} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/ui/app_list/arc/arc_default_app_list.cc diff]

chrome/browser/ui/app_list/arc/arc_default_app_list.h diff]

chrome/test/data/arc_board_default_apps/test_app2.json [Renamed from chrome/test/data/arc_default_apps/test_app2.json - diff

chrome/test/data/arc_board_default_apps/test_app2/icon_100p_48.png [Renamed from chrome/test/data/arc_default_apps/test_app2/icon_100p_48.png - diff

chrome/test/data/arc_board_default_apps/test_app2/icon_100p_64.png [Renamed from chrome/test/data/arc_default_apps/test_app2/icon_100p_64.png - diff

chrome/test/data/arc_board_default_apps/test_app2/icon_200p_48.png [Renamed from chrome/test/data/arc_default_apps/test_app2/icon_200p_48.png - diff

chrome/test/data/arc_board_default_apps/test_app2/icon_200p_64.png [Renamed from chrome/test/data/arc_default_apps/test_app2/icon_200p_64.png - diff

commit e1956361fb465a29fa48d17373fb9865245f18ee author Henrique Grandinetti <hgrandinetti@chromium.org> Thu Oct 11 23:36:59 2018 committer Aga Wronska <agawronska@chromium.org> Thu Oct 11 23:36:59 2018 Handle null times on UsageTimeLimitProcessor and reset usage time when inactive Bug: 894047 Change-Id: I3858a8ae44fe622d1c9fc64e2ee544368f9ba725 Reviewed-on: https://chromium-review.googlesource.com/c/1274406 Reviewed-by: Rahul Chaturvedi <rkc@chromium.org> Reviewed-by: Michael Giuffrida <michaelpg@chromium.org> Reviewed-by: Sergey Poromov <poromov@chromium.org> Commit-Queue: Henrique Grandinetti <hgrandinetti@google.com> Cr-Original-Commit-Position: refs/heads/master@{#598945}(cherry picked from commit 42232057e1321c01c12817367325185beb1a1128) Reviewed-on: https://chromium-review.googlesource.com/c/1277487 Reviewed-by: Aga Wronska <agawronska@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#977} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/chromeos/child_accounts/usage_time_limit_processor.cc diff]

chrome/browser/chromeos/child_accounts/usage_time_limit_processor_unittest.cc diff]

chrome/browser/chromeos/policy/device_status_collector.cc diff]

chrome/browser/chromeos/policy/device_status_collector.h diff]

commit c87a29ea34066360632c9362464ba376685bf85c author Ivan Sandrk <isandrk@google.com> Thu Oct 11 23:06:16 2018 committer Ivan Šandrk <isandrk@chromium.org> Thu Oct 11 23:06:16 2018 [M70 Merge][Locked Fullscreen] Fix regression in locked fullscreen mode crrev.com/c/1156995 introduced a regression in locked fullscreen mode where it became possible to exit the mode using the controls that auto-hide at the top of the screen (normally they should be disabled in locked fullscreen mode). Fix this by disabling immersive mode if we're in locked fullscreen, and also disable the FullscreenControlHost which shows a bubble exit target when no other UI is shown. TBR=isandrk@chromium.org (cherry picked from commit 29a551c095f3df8e42a5c95994150b226a1d36f8) Bug: 883104 Change-Id: I489e471aed2b3f9f809ad1d11f76b37d6c6b4a00 Reviewed-on: https://chromium-review.googlesource.com/c/1234334 Commit-Queue: Ivan Šandrk <isandrk@chromium.org> Reviewed-by: Scott Violet <sky@chromium.org> Reviewed-by: Ken Buchanan <kenrb@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598879} Reviewed-on: https://chromium-review.googlesource.com/c/1277986 Reviewed-by: Ivan Šandrk <isandrk@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#976} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} ash/public/cpp/window_pin_type.cc diff]

ash/public/cpp/window_pin_type.h diff]

ash/public/cpp/window_state_type.cc diff]

ash/public/cpp/window_state_type.h diff]

ash/public/interfaces/window_state_type.mojom diff]

chrome/browser/ui/browser_command_controller_unittest.cc diff]

chrome/browser/ui/exclusive_access/exclusive_access_context.h diff]

chrome/browser/ui/exclusive_access/fullscreen_controller_state_unittest.cc diff]

chrome/browser/ui/views/apps/chrome_native_app_window_views_aura_ash.cc diff]

chrome/browser/ui/views/apps/chrome_native_app_window_views_aura_ash.h diff]

chrome/browser/ui/views/frame/browser_non_client_frame_view.cc diff]

chrome/browser/ui/views/frame/browser_non_client_frame_view.h diff]

chrome/browser/ui/views/frame/browser_non_client_frame_view_ash.cc diff]

chrome/browser/ui/views/frame/browser_non_client_frame_view_ash.h diff]

chrome/browser/ui/views/frame/browser_view.cc diff]

chrome/browser/ui/views/frame/browser_view.h diff]

chrome/browser/ui/views/frame/immersive_mode_controller_ash.cc diff]

chrome/browser/ui/views/fullscreen_control/fullscreen_control_host.cc diff]

chrome/browser/ui/views/media_router/presentation_receiver_window_view.cc diff]

chrome/browser/ui/views/media_router/presentation_receiver_window_view.h diff]

commit 156b810486bb513310dcf7e7db701937f2da02f6 author Alexander Hendrich <hendrich@chromium.org> Thu Oct 11 22:58:12 2018 committer Alexander Hendrich <hendrich@chromium.org> Thu Oct 11 22:58:12 2018 [Merge M70] Fix crash in NetworkCertLoader on shutdown On shutdown we remove remaining PolicyCertificateProviders from NetworkCertLoader. This triggered OnCertCacheOrPolicyCertsUpdated(), which also read from the user's NSS database, which might be deleted during shutdown already. This CL fixes this by adding an additional cache |all_certs_from_cache_|, which gets updated by updates from the CertCaches (triggered from NSS database). Removing a PolicyCertificateProvider will only read from |all_certs_from_cache_| instead of reading from the deleted NSS database again. (manually cherry picked from commit ad0e0e70714dd985b4caa62a31a147edb24f25a3) Bug: 893642 Change-Id: I26d7ec5a66df9c9bd97929ca19c5cefa0183f06f Reviewed-on: https://chromium-review.googlesource.com/c/1276985 Commit-Queue: Alexander Hendrich <hendrich@chromium.org> Reviewed-by: Steven Bennetts <stevenjb@chromium.org> Reviewed-by: Pavol Marko <pmarko@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/c/1277447 Cr-Commit-Position: refs/branch-heads/3538@{#975} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chromeos/cert_loader.cc diff]

chromeos/cert_loader.h diff]

commit e35b1ad216fa7ef04b66177d49f692976ad8bf5d author John Abd-El-Malek <jam@chromium.org> Thu Oct 11 22:28:27 2018 committer John Abd-El-Malek <jam@chromium.org> Thu Oct 11 22:28:27 2018 Fix DataPipe(capacity) constructor not to double-allocate. The DataPipe(capacity) constructor was previously creating a DataPipe on the stack, using the DataPipe(options) constructor, but then not using it, and instead manually creating the pipe handles to return to the caller. Remove the wasted work, and clean up some ALLOW_UNUSED_LOCAL() that are no longer required, since DCHECKs in DataPipe() constructors were replaced with CHECKs. Bug: 892297, 890468 Reviewed-on: https://chromium-review.googlesource.com/c/1266602 Reviewed-by: Ken Rockot <rockot@chromium.org> Commit-Queue: Wez <wez@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#597623} Change-Id: Ic83e3d4fe00808e1fd95acb283e62a2f9d78a3a4 Reviewed-on: https://chromium-review.googlesource.com/c/1277682 Reviewed-by: John Abd-El-Malek <jam@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#974} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} mojo/public/cpp/system/data_pipe.h diff]

commit f7b184785d3610465304a0eb75a0216e405a55bf author chrome-release-bot <chrome-release-bot@chromium.org> Thu Oct 11 22:13:36 2018 committer chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Thu Oct 11 22:13:36 2018 Incrementing VERSION to 70.0.3538.62 TBR=mmoss@chromium.org Change-Id: If97f2037e8a99b13978b33ef162570cca8777967 Reviewed-on: https://chromium-review.googlesource.com/c/1278225 Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#973} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/VERSION diff]

commit 1384fef05680a7ff333f9eb08439ae61c14f1d49 author Mustafa Emre Acer <meacer@chromium.org> Thu Oct 11 22:00:31 2018 committer Mustafa Emre Acer <meacer@chromium.org> Thu Oct 11 22:00:31 2018 [Merge to M70] Fix crashes in site engagement check of lookalike URL navigations net::registry_controlled_domains::GetDomainAndRegistry can return empty string if the passed domain isn't registry controlled. This CL handles those cases. TBR=meacer@chromium.org (cherry picked from commit 562cdd396ac998ea756650d26c2cb9495c881b81) Bug: 889843 Change-Id: I7d09aaeb886f4ec8ff5caddc991889a598c73aa1 Reviewed-on: https://chromium-review.googlesource.com/c/1263563 Commit-Queue: Mustafa Emre Acer <meacer@chromium.org> Reviewed-by: Tommy Li <tommycli@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598061} Reviewed-on: https://chromium-review.googlesource.com/c/1278136 Reviewed-by: Mustafa Emre Acer <meacer@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#972} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/ui/omnibox/lookalike_url_navigation_observer.cc diff]

chrome/browser/ui/omnibox/lookalike_url_navigation_observer_browsertest.cc diff]

commit ea8cdc51edb91a60f3b9318740688231c2f44a39 author chrome-release-bot <chrome-release-bot@chromium.org> Thu Oct 11 21:43:24 2018 committer chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Thu Oct 11 21:43:24 2018 Incrementing VERSION to 70.0.3538.61 TBR=amineer@chromium.org Change-Id: Ie780f60b01618c61c48a9dd31aafba0658793125 Reviewed-on: https://chromium-review.googlesource.com/c/1277555 Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#971} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/VERSION diff]

commit 3e8b2f448143a6a1d06178082cfd1ec8b6b46c07 author khmel@chromium.org <khmel@chromium.org> Thu Oct 11 21:30:39 2018 committer Yury Khmel <khmel@chromium.org> Thu Oct 11 21:30:39 2018 [Merge M70] arc: Fix crash in ARC app search provider (multi-profile mode) We allow using multiple profiles but ARC works only with primary. This checks this condition (wider case) and does not create provider. TEST=Manually. no longer crash. BUG=891749 TBR=khmel@chromium.org (cherry picked from commit bcc1628c4a0d4dc5205352b8a3441fba3340ceda) Change-Id: I706f2c4c6f10e0eb889d52d546d4a7bc34459d99 Reviewed-on: https://chromium-review.googlesource.com/c/1277377 Commit-Queue: Yury Khmel <khmel@chromium.org> Reviewed-by: Xiyuan Xia <xiyuan@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598898} Reviewed-on: https://chromium-review.googlesource.com/c/1278128 Reviewed-by: Yury Khmel <khmel@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#970} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/ui/app_list/search/search_controller_factory.cc diff]

commit ad4212eb23008bd9dc79e81e2e0451bf5bd48629 author Pedro Amaral <amaralp@chromium.org> Thu Oct 11 21:20:30 2018 committer Pedro Amaral <amaralp@chromium.org> Thu Oct 11 21:20:30 2018 Hide HTS toggle when accessibility is enabled Hide HTS toggle when accessibility is enabled. Also fixed accessibility string for tabs. I had originally followed what AccessibilityTabModelWrapper.java did but it turned out there was a bug in that class: https://bugs.chromium.org/p/chromium/issues/detail?id=886975 (cherry picked from commit f6a8e159b31a0e487eb66b9272fd6b231b3cfc4d) Bug: 892638 Change-Id: Ief4a3c65b46d75ef3ffc9eb3786c0d26eac94c7d Reviewed-on: https://chromium-review.googlesource.com/c/1275028 Reviewed-by: Yusuf Ozuysal <yusufo@chromium.org> Commit-Queue: Pedro Amaral <amaralp@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598846} Reviewed-on: https://chromium-review.googlesource.com/c/1277964 Reviewed-by: Pedro Amaral <amaralp@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#969} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/android/java/src/org/chromium/chrome/browser/toolbar/IncognitoToggleTabLayout.java diff]

chrome/android/java/src/org/chromium/chrome/browser/toolbar/ToolbarPhone.java diff]

commit ebacf403c9b00332746b18d085a25061078a29ad author François Beaufort <beaufort.francois@gmail.com> Thu Oct 11 20:16:03 2018 committer François Beaufort <beaufort.francois@gmail.com> Thu Oct 11 20:16:03 2018 Picture-in-Picture: check that pip_player matches player_id. This makes sure we don't reset media_player_id_ when switching non-Mediastream Picture-in-Picture video to a Mediastream video. Bug: 872066, 893830 Change-Id: Ie84b51ae1f7e0ac822743dfeb948bea6afd076ba Reviewed-on: https://chromium-review.googlesource.com/c/1273515 Reviewed-by: Jochen Eisinger <jochen@chromium.org> Reviewed-by: Mounir Lamouri <mlamouri@chromium.org> Commit-Queue: François Beaufort <beaufort.francois@gmail.com> Cr-Original-Commit-Position: refs/heads/master@{#598428}(cherry picked from commit c0dc584775e65fc731a62ccbbb1dceb09fc4a86e) Reviewed-on: https://chromium-review.googlesource.com/c/1277985 Reviewed-by: François Beaufort <beaufort.francois@gmail.com> Cr-Commit-Position: refs/branch-heads/3538@{#968} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/picture_in_picture/picture_in_picture_window_controller_browsertest.cc diff]

chrome/test/data/media/picture-in-picture/window-size.html diff]

content/browser/media/media_web_contents_observer.cc diff]

commit 0aee1e17390a6df938508215b42b6f748e78c65f author David Roger <droger@chromium.org> Thu Oct 11 19:04:18 2018 committer David Roger <droger@chromium.org> Thu Oct 11 19:04:18 2018 [settings] Fix signout link and footer for the Clear Browsing Data dialog Clicking the link was triggering the wrong action: signout instead of pausing sync. The footer was also incorrectly displayed when Dice is disabled. TBR=droger@chromium.org (cherry picked from commit 302abf6e0b50650aa1ae5869cab9c56af0007629) Bug: 893228 Change-Id: Ieb88f89e83c8c0a4173ca6d61efbf1b10126f822 Reviewed-on: https://chromium-review.googlesource.com/c/1270901 Commit-Queue: Thomas Tangl <tangltom@chromium.org> Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org> Reviewed-by: Thomas Tangl <tangltom@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598385} Reviewed-on: https://chromium-review.googlesource.com/c/1275951 Reviewed-by: David Roger <droger@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#966} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/resources/settings/clear_browsing_data_dialog/clear_browsing_data_dialog.html diff]

chrome/browser/resources/settings/clear_browsing_data_dialog/clear_browsing_data_dialog.js diff]

chrome/browser/resources/settings/people_page/sync_browser_proxy.js diff]

chrome/browser/resources/settings/settings_resources.grd diff]

chrome/browser/ui/webui/settings/people_handler.cc diff]

chrome/browser/ui/webui/settings/people_handler.h diff]

chrome/test/data/webui/settings/cr_settings_browsertest.js diff]

chrome/test/data/webui/settings/privacy_page_test.js diff]

chrome/test/data/webui/settings/test_sync_browser_proxy.js diff]

commit 8509662e868c471a545845194860550244277901 author Peng Huang <penghuang@chromium.org> Thu Oct 11 18:52:06 2018 committer Peng Huang <penghuang@chromium.org> Thu Oct 11 18:52:06 2018 Disable GL_EXT_timer_query on Linux with VMware GPU. Bug: 811661 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 Change-Id: I4bdcc4edf654c8c46c5015a1b4e6bc42ca79c381 Reviewed-on: https://chromium-review.googlesource.com/1239220 Reviewed-by: Antoine Labour <piman@chromium.org> Commit-Queue: Peng Huang <penghuang@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#593532}(cherry picked from commit 8d70ab51e28e4c1f3ac01465f7a7a1cea889181b) Reviewed-on: https://chromium-review.googlesource.com/c/1277595 Reviewed-by: Peng Huang <penghuang@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#965} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} gpu/config/gpu_driver_bug_list.json diff]

commit 8ac09d7134d4fb344ba1c682517ee87cb56e45a6 author Matthew Jones <mdjones@chromium.org> Thu Oct 11 17:24:14 2018 committer Matthew Jones <mdjones@chromium.org> Thu Oct 11 17:24:14 2018 Fix status bar color on tablets This patch adds a check for tablet to the theme color logic that runs on startup. Now the status bar on tablets is always black. TBR=mdjones@chromium.org (cherry picked from commit 992af589661369d557a69e73f3390ef956b8aea2) Bug: 894209 Change-Id: I01b1309e4da48da2932ce6661aaa1ce35404379d Reviewed-on: https://chromium-review.googlesource.com/c/1274612 Reviewed-by: Theresa <twellington@chromium.org> Commit-Queue: Matthew Jones <mdjones@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598574} Reviewed-on: https://chromium-review.googlesource.com/c/1277365 Reviewed-by: Matthew Jones <mdjones@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#964} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/android/java/res/values-sw600dp-v26/styles.xml [Added - diff

chrome/android/java/src/org/chromium/chrome/browser/ChromeActivity.java diff]

commit 199e925fc7002ec19a29ed9e2db7a68e0feb77f7 author Ivan Sandrk <isandrk@google.com> Thu Oct 11 17:17:38 2018 committer Ivan Šandrk <isandrk@chromium.org> Thu Oct 11 17:17:38 2018 [M70 Merge][TPM Reporting] Add TPM status information to DeviceStatusCollector Recently there was a serious problem where a lot of TPMs ended up in a locked state due to unforeseen interactions of several components. In order to get a better understanding of the scope of the problem we want to have accurate reporting on TPM status of the devices. TBR=isandrk@chromium.org (cherry picked from commit 2439f0be105b97464e15cf6e6c9ff42c74c15018) Bug: 893245 Change-Id: I41de153ac6887d6d48a106f64211fba0f104cac1 Reviewed-on: https://chromium-review.googlesource.com/c/1269040 Reviewed-by: James Cook <jamescook@chromium.org> Reviewed-by: Ryo Hashimoto <hashimoto@chromium.org> Reviewed-by: Sergey Poromov <poromov@chromium.org> Commit-Queue: Ivan Šandrk <isandrk@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598687} Reviewed-on: https://chromium-review.googlesource.com/c/1277285 Reviewed-by: Ivan Šandrk <isandrk@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#963} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/chromeos/child_accounts/consumer_status_reporting_service.cc diff]

chrome/browser/chromeos/policy/device_cloud_policy_manager_chromeos.cc diff]

chrome/browser/chromeos/policy/device_status_collector.cc diff]

chrome/browser/chromeos/policy/device_status_collector.h diff]

chrome/browser/chromeos/policy/device_status_collector_browsertest.cc diff]

chrome/browser/chromeos/policy/status_uploader_unittest.cc diff]

chromeos/dbus/cryptohome_client.cc diff]

chromeos/dbus/cryptohome_client.h diff]

chromeos/dbus/fake_cryptohome_client.cc diff]

chromeos/dbus/fake_cryptohome_client.h diff]

components/policy/proto/device_management_backend.proto diff]

commit b9d14b2962bd679a1b6db55e5eedd96b6d37a805 author Toni Barzic <tbarzic@google.com> Thu Oct 11 17:11:05 2018 committer Toni Baržić <tbarzic@chromium.org> Thu Oct 11 17:11:05 2018 Work around SIM activation UI showing a blank page Mobile activation flow creates and submits a form inside a webview. The form is generated from the information provided with the SIM, and is expected to redirect to the carrier's mobile activation site. For some reason, currently the page loaded in the webview just after the form has been submitted is blank (instead of showing mobile activation UI). To work around this, pending further investigation, reload the webview after the initial navigation to the carrier site is committed, as that seems to help with the problem - after the webview is reloaded the carrier activation UI is properly displayed. BUG=893248 TBR=stevenjb@chromium.org Change-Id: I7ef822fae66d9d41488ebe2d57fbddba8dd60f09 Reviewed-on: https://chromium-review.googlesource.com/c/1274450 Reviewed-by: Steven Bennetts <stevenjb@chromium.org> Commit-Queue: Toni Baržić <tbarzic@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598558}(cherry picked from commit c8257eb48974d7d72b799c3c8452baad90fc0eaf) Reviewed-on: https://chromium-review.googlesource.com/c/1277165 Reviewed-by: Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#962} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/resources/chromeos/mobile_setup.js diff]

commit f92d7868a16e428462bd03771680563eb13f83cf author chrome-release-bot <chrome-release-bot@chromium.org> Thu Oct 11 17:00:23 2018 committer chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Thu Oct 11 17:00:23 2018 Incrementing VERSION to 70.0.3538.60 TBR=amineer@chromium.org Change-Id: I3977940a33950567c75e46eefe7388ab6692483d Reviewed-on: https://chromium-review.googlesource.com/c/1277008 Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#961} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/VERSION diff]

commit 15c479439d8c6c0ddf089180c213d03f49e983dc author John Budorick <jbudorick@chromium.org> Thu Oct 11 16:41:21 2018 committer John Budorick <jbudorick@chromium.org> Thu Oct 11 16:41:21 2018 3538: Add ios/web/public to ios/chrome/browser/ui/tab_grid:tab_grid_ui deps. Not sure yet why this isn't breaking M71, but it's breaking M70. Bug: 894429 Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs Change-Id: I7eadef0d8a6e990e37300ec0b391f05c1220ec0d Reviewed-on: https://chromium-review.googlesource.com/c/1276566 Commit-Queue: Mark Cogan <marq@chromium.org> Reviewed-by: Mark Cogan <marq@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598786}(cherry picked from commit 71de919028d9bed06528f814e0a469e127344110) Reviewed-on: https://chromium-review.googlesource.com/c/1276886 Reviewed-by: edchin <edchin@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#960} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} ios/chrome/browser/ui/tab_grid/BUILD.gn diff]

commit b6f09861adf7e5c72a4898500ea83a4cf3e13608 author Sergey Poromov <poromov@chromium.org> Thu Oct 11 14:11:36 2018 committer Sergey Poromov <poromov@chromium.org> Thu Oct 11 14:11:36 2018 Increase kiosk splash screen min time. Increasing from 3 to 10 seconds as it now takes around 3 seconds to show the screen on the slow devices. This is an easy temporary fix. Perfectly, controller should start timer only when splash screen is actually shown. Bug: 890368 Change-Id: I2048a54c1df7f2474cc29eb1d00e06bac3ff1e7f Reviewed-on: https://chromium-review.googlesource.com/c/1264635 Reviewed-by: Jacob Dufault <jdufault@chromium.org> Commit-Queue: Sergey Poromov <poromov@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#597265}(cherry picked from commit fe45d4757c0f4dc339c6a0b4e79aaf7a99c122a3) Reviewed-on: https://chromium-review.googlesource.com/c/1270738 Reviewed-by: Sergey Poromov <poromov@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#959} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/browser/chromeos/login/app_launch_controller.cc diff]

chrome/browser/chromeos/login/arc_kiosk_controller.cc diff]

commit db39c183320b578fda5d3dfeea1a2c2280762eb1 author Giovanni Ortuño Urquidi <ortuno@chromium.org> Thu Oct 11 04:40:17 2018 committer Giovanni Ortuño Urquidi <ortuno@chromium.org> Thu Oct 11 04:40:17 2018 Reland "bluetooth: Unpause discovery during destruction if there is a pending connection" This is a reland of d1c20525b9449cf889bc5be5e42529ea20e425c0 Original change's description: > bluetooth: Unpause discovery during destruction if there is a pending connection > > A device could get removed after pausing discovery but before initiating > a connection. This could lead us to never unpausing discovery. > > This CL unpauses discovery if there is a pending connection during > destruction. > > Bug: 883975 > Change-Id: I679f468526b97a62a350af74f51fcecd8acd7635 > Reviewed-on: https://chromium-review.googlesource.com/c/1272739 > Reviewed-by: Reilly Grant <reillyg@chromium.org> > Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org> > Cr-Original-Commit-Position: refs/heads/master@{#598601}(cherry picked from commit aa7581667e72b3d2d2cb2321e4861173183cfba2) > Reviewed-on: https://chromium-review.googlesource.com/c/1275485 > Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org> > Cr-Commit-Position: refs/branch-heads/3538@{#953} > Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} Bug: 883975 Change-Id: I728b9a74c151c6d05334eabf4b53ba3b5ccbfe43 Reviewed-on: https://chromium-review.googlesource.com/c/1275646 Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#958} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} device/bluetooth/bluez/bluetooth_bluez_unittest.cc diff]

device/bluetooth/bluez/bluetooth_device_bluez.cc diff]

device/bluetooth/dbus/fake_bluetooth_device_client.cc diff]

device/bluetooth/dbus/fake_bluetooth_device_client.h diff]

commit e6102d1aa16167382fedec5d7bbbebc9a59f82c1 author chrome-release-bot <chrome-release-bot@chromium.org> Thu Oct 11 04:32:13 2018 committer chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Thu Oct 11 04:32:13 2018 Incrementing VERSION to 70.0.3538.59 TBR=mmoss@chromium.org Change-Id: Iff7461dbe504b5dc4ba436e994c4bb9f63c52ae4 Reviewed-on: https://chromium-review.googlesource.com/c/1275172 Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#957} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} chrome/VERSION diff]

commit 02d7e4fb96513421e1be60070a58e9533a434a11 author Giovanni Ortuño Urquidi <ortuno@chromium.org> Thu Oct 11 04:28:09 2018 committer Giovanni Ortuño Urquidi <ortuno@chromium.org> Thu Oct 11 04:28:09 2018 Revert "bluetooth: Unpause discovery during destruction if there is a pending connection" This reverts commit d1c20525b9449cf889bc5be5e42529ea20e425c0. Reason for revert: UnpauseDiscovery is not present in M70 Original change's description: > bluetooth: Unpause discovery during destruction if there is a pending connection > > A device could get removed after pausing discovery but before initiating > a connection. This could lead us to never unpausing discovery. > > This CL unpauses discovery if there is a pending connection during > destruction. > > Bug: 883975 > Change-Id: I679f468526b97a62a350af74f51fcecd8acd7635 > Reviewed-on: https://chromium-review.googlesource.com/c/1272739 > Reviewed-by: Reilly Grant <reillyg@chromium.org> > Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org> > Cr-Original-Commit-Position: refs/heads/master@{#598601}(cherry picked from commit aa7581667e72b3d2d2cb2321e4861173183cfba2) > Reviewed-on: https://chromium-review.googlesource.com/c/1275485 > Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org> > Cr-Commit-Position: refs/branch-heads/3538@{#953} > Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} TBR=ortuno@chromium.org Change-Id: I4768c4fe3bd9c4e66f917dd050714dd376dac10f No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 883975 Reviewed-on: https://chromium-review.googlesource.com/c/1275645 Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#956} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} device/bluetooth/bluez/bluetooth_bluez_unittest.cc diff]

device/bluetooth/bluez/bluetooth_device_bluez.cc diff]

device/bluetooth/dbus/fake_bluetooth_device_client.cc diff]

device/bluetooth/dbus/fake_bluetooth_device_client.h diff]

commit a78abe015bdac24cbd8ea1015d5973c69d493647 author edchin <edchin@chromium.org> Thu Oct 11 03:50:49 2018 committer edchin <edchin@chromium.org> Thu Oct 11 03:50:49 2018 Merge to release branch [ios] ClosingLastIncognitoTab flag disabled by default Turn off flag by default so it can be rolled out via experiment. TBR=pkl@chromium.org (cherry picked from commit dd8f33f8d296c893869967b1936768079de9a3e7) Bug: 891396 Change-Id: I1a628ad430edbe225e1906b66d950632c73f3d05 Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs Reviewed-on: https://chromium-review.googlesource.com/c/1274840 Reviewed-by: edchin <edchin@chromium.org> Reviewed-by: Peter Lee <pkl@chromium.org> Commit-Queue: edchin <edchin@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598614} Reviewed-on: https://chromium-review.googlesource.com/c/1275171 Cr-Commit-Position: refs/branch-heads/3538@{#955} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} ios/chrome/browser/ui/ui_feature_flags.cc diff]

commit 6a992c50b5fddf82bd287022cdaff02346cfaa9b author edchin <edchin@chromium.org> Thu Oct 11 03:40:00 2018 committer edchin <edchin@chromium.org> Thu Oct 11 03:40:00 2018 Merge to release branch [ios] Improve page change due to closing last incognito tab This CL: 1) Adds a slight delay to the page change animation after the user closes the last incognito tab when the tab switcher is visible. 2) Reduces flash when the user closes the last incognito tab when not in the tab switcher. 3) Adds the behavior of automatically switching to the regular tabs panel after closing the last incognito tab behind a flag. TBR=pkl@chromium.org (cherry picked from commit 18a3e60dc9a297f4ad1aa6ab32587f6079f5e0b8) Bug: 891396 Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs Change-Id: I00f0948a9f61c6df005ae03009a1f3c336faa244 Reviewed-on: https://chromium-review.googlesource.com/c/1266214 Commit-Queue: edchin <edchin@chromium.org> Reviewed-by: Peter Lee <pkl@chromium.org> Reviewed-by: edchin <edchin@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#597730} Reviewed-on: https://chromium-review.googlesource.com/c/1275169 Cr-Commit-Position: refs/branch-heads/3538@{#954} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} ios/chrome/browser/about_flags.mm diff]

ios/chrome/browser/ios_chrome_flag_descriptions.cc diff]

ios/chrome/browser/ios_chrome_flag_descriptions.h diff]

ios/chrome/browser/ui/tab_grid/tab_grid_constants.h diff]

ios/chrome/browser/ui/tab_grid/tab_grid_constants.mm diff]

ios/chrome/browser/ui/tab_grid/tab_grid_view_controller.mm diff]

ios/chrome/browser/ui/ui_feature_flags.cc diff]

ios/chrome/browser/ui/ui_feature_flags.h diff]

ios/chrome/browser/ui/ui_util.h diff]

ios/chrome/browser/ui/ui_util.mm diff]

commit d1c20525b9449cf889bc5be5e42529ea20e425c0 author Giovanni Ortuño Urquidi <ortuno@chromium.org> Thu Oct 11 02:05:58 2018 committer Giovanni Ortuño Urquidi <ortuno@chromium.org> Thu Oct 11 02:05:58 2018 bluetooth: Unpause discovery during destruction if there is a pending connection A device could get removed after pausing discovery but before initiating a connection. This could lead us to never unpausing discovery. This CL unpauses discovery if there is a pending connection during destruction. Bug: 883975 Change-Id: I679f468526b97a62a350af74f51fcecd8acd7635 Reviewed-on: https://chromium-review.googlesource.com/c/1272739 Reviewed-by: Reilly Grant <reillyg@chromium.org> Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#598601}(cherry picked from commit aa7581667e72b3d2d2cb2321e4861173183cfba2) Reviewed-on: https://chromium-review.googlesource.com/c/1275485 Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org> Cr-Commit-Position: refs/branch-heads/3538@{#953} Cr-Branched-From: 79f7c91a2b2a2932cd447fa6f865cb6662fa8fa6-refs/heads/master@{#587811} device/bluetooth/bluez/bluetooth_bluez_unittest.cc diff]

device/bluetooth/bluez/bluetooth_device_bluez.cc diff]

device/bluetooth/dbus/fake_bluetooth_device_client.cc diff]

device/bluetooth/dbus/fake_bluetooth_device_client.h diff]