Publish DEPS for 68.0.3440.70
Incrementing VERSION to 68.0.3440.70
[email protected]
Change-Id: I5bfa09fbbd27367cf7427a1c9ad3409fc65c3e75
Reviewed-on: https://chromium-review.googlesource.com/1142596
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#718}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
assistant: disable assistant on M68.
This fixes crash due to assistant initialization timing.
Bug: 850762
Test: Manual
Change-Id: I5bd2a81f5f8a93e8f3d6f1745bf330f7a7c11260
Reviewed-on: https://chromium-review.googlesource.com/1130546
Reviewed-by: Xiaohui Chen <[email protected]>
Reviewed-by: James Cook <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#717}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Enable enterprise.reportingPrivate API on Stable.
Change-Id: I1bbeefa0bb68da658443e65ed1f9d63a510c4ed8
Bug: 826298
Reviewed-on: https://chromium-review.googlesource.com/1141050
Reviewed-by: Devlin <[email protected]>
Commit-Queue: Georges Khalil <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#575854}(cherry picked from commit 0eae27d80e7499c5740580c960c6bf73c81c9865)
Reviewed-on: https://chromium-review.googlesource.com/1142664
Reviewed-by: Georges Khalil <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#716}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Disable glClear on Mali T720 12.1.01alp0
glClear appears to crash on this device. Enabling the "gl_clear_broken"
workaround.
[email protected]
(cherry picked from commit 3c98e778faedf80d25556f9f2dc985985ca31c99)
BUG: 860418
Change-Id: I06ff00e2aa7523b43e283bcdc09b2d36ceacf4e4
Reviewed-on: https://chromium-review.googlesource.com/1137784
Reviewed-by: Antoine Labour <[email protected]>
Commit-Queue: Eric Karl <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#576163}
Reviewed-on: https://chromium-review.googlesource.com/1142531
Reviewed-by: Eric Karl <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#715}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.69
[email protected]
Change-Id: Ie9b44779b4417d950e589e758161bacb28b0c0f3
Reviewed-on: https://chromium-review.googlesource.com/1142042
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#714}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
fix build error, file was moved
Bug: 864889
Change-Id: Ica61026c2ebcc02e6424f8f6665baf1be133c4ff
Reviewed-on: https://chromium-review.googlesource.com/1141986
Reviewed-by: Justin DeWitt <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#713}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
DevTools: Restore colorpicker functionality on pre-m67 custom palettes
Bug:851311
Change-Id: Ia13bc1f082b69f37ee8ca65ac467cea166c11a2b
Reviewed-on: https://chromium-review.googlesource.com/1120951
Commit-Queue: Andrey Lushnikov <[email protected]>
Reviewed-by: Andrey Lushnikov <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#572146}(cherry picked from commit 426c0fc678846f56a905eca26feb182b34742bf6)
Reviewed-on: https://chromium-review.googlesource.com/1140461
Reviewed-by: Paul Irish <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#712}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
desktop-pwas: Don't check offline state for Desktop PWAs
Cherry pick of c1c7c251887831a406eb9a94f24ae7084c59abca for 68
FindMatchingUrlHandler checks if the Chrome app supports offline and if
not returns no matching URL handlers. This is done in order to avoid
redirecting links to apps that don't support offline.
Unfortunately, this offline check causes problems for Desktop PWAs.
Desktop PWAs use FindMatchingUrlHandler to decide if a URL belongs to an
app. Because of the check in FindMatchingUrlHandler, it seems as if no
URLs belong to the app.
To solve the issue, we introduce separate methods to be used by
Bookmark Apps and Platform Apps. The Platform Apps method checks
for offline and the Bookmark Apps one does not.
[email protected],[email protected],[email protected]
Bug: 850626
Change-Id: I7560be15df73c51f040db2796dbce0fa3ca758fe
Reviewed-on: https://chromium-review.googlesource.com/1140342
Reviewed-by: Giovanni Ortuño Urquidi <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#711}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.68
[email protected]
Change-Id: I44c7096fe996676684d53341c0128173afad4544
Reviewed-on: https://chromium-review.googlesource.com/1141268
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#710}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Adjust out-of-flow position for rtl container with left-hand scrollbar
Cherry-picked from:
https://chromium-review.googlesource.com/1125335
BUG=832569
[email protected],[email protected]
Change-Id: I7d2f26800ed5a410b0cca9bb61bf7529c2298536
Reviewed-on: https://chromium-review.googlesource.com/1141213
Reviewed-by: Stefan Zager <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#709}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[M68 branch] Add Lao/Thai spoofable entries
U+0E1E (พ) => w
U+0E9E (ພ) => w
U+0E9F (ຟ) => w
U+0EA3 (ຣ) => s
U+0EAE (ຮ) => s
U+0E1A (บ) => u
U+0E9A (ບ) => u
Note that U+0E1F(ฟ) and U+0E23 (ร) were added a while ago.
BUG=833143
TEST=components_unittests --gtest_filter=*IDN*
[email protected],[email protected]
Change-Id: I882e7d272cdca1d80aa23be94b4d7906ff8653c1
Reviewed-on: https://chromium-review.googlesource.com/1058710
Reviewed-by: Peter Kasting <[email protected]>
Commit-Queue: Jungshik Shin <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#562565}
Reviewed-on: https://chromium-review.googlesource.com/1141215
Reviewed-by: Jungshik Shin <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#708}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.67
[email protected]
Change-Id: Ie92f43660a68bec131a78911cbd83e8751879083
Reviewed-on: https://chromium-review.googlesource.com/1141224
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#707}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Merge M68][Autofill] Modify origin to only keep settings or empty.
Since the only use Autofill has for the origin is checking whether
is is equal to the settings origin, the only values we should keep
are the settings origin and empty.
I'll prepare a follow-up CL where this string is changed to an enum.
[email protected]
Change-Id: I6f1a5647670d4e5228be4d625db650cab38dcc5a
Reviewed-on: https://chromium-review.googlesource.com/1136933
Commit-Queue: Sebastien Seguin-Gagnon <[email protected]>
Reviewed-by: Mathieu Perreault <[email protected]>
Reviewed-by: Christian Dullweber <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#575306}
Reviewed-on: https://chromium-review.googlesource.com/1140929
Cr-Commit-Position: refs/branch-heads/3440@{#706}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
M68: service worker: Gate eager CacheStorage setup behind a feature flag.
This will enable us to disable the optimization via a field trial kill
switch if needed.
(cherry picked from commit c25fea4b813655a45ff64a1d6f523504733b9e02)
Bug: 854905
Change-Id: Ic312cbedd7685761a45fee986061767b14295afa
Reviewed-on: https://chromium-review.googlesource.com/1139457
Reviewed-by: Kinuko Yasuda <[email protected]>
Commit-Queue: Matt Falkenhagen <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#575566}
TBR: kinuko
Reviewed-on: https://chromium-review.googlesource.com/1140338
Reviewed-by: Matt Falkenhagen <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#705}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
M68: service worker: Eagerly provide CacheStoragePtr at worker startup.
Most service workers will need CacheStoragePtr in a performance
sensitive way. We discovered there is slowness using InterfaceProvider
to get the ptr on first use after worker startup.
(cherry picked from commit d1d43314ace95237cea594fd77a262dfdffb1e4b)
Bug: 854905
Change-Id: Iefcd8910d1b8b6ba1cfcc4df79c213abde0f9e3a
Reviewed-on: https://chromium-review.googlesource.com/1124130
Commit-Queue: Matt Falkenhagen <[email protected]>
Reviewed-by: Makoto Shimazu <[email protected]>
Reviewed-by: Kinuko Yasuda <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#572544}
TBR: shimazu, kinuko
Reviewed-on: https://chromium-review.googlesource.com/1140337
Reviewed-by: Matt Falkenhagen <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#704}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Throttle url download requests from a RenderFrame
RenderFrameImpl::DownloadUrl() can be abused to trigger a large number
of download to overwhelm the browser process.
This CL rate limits the number of download to a maximum of 10 per second.
Bug: 860045
Change-Id: I490ae3a99eb59aef709b9f1e6be5eb0f787354f4
Reviewed-on: https://chromium-review.googlesource.com/1132485
Commit-Queue: Min Qin <[email protected]>
Reviewed-by: John Abd-El-Malek <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#574078}(cherry picked from commit a13cb2a1020b933c070d9db84fbc48dae5b0e1c6)
Reviewed-on: https://chromium-review.googlesource.com/1140457
Reviewed-by: Min Qin <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#703}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Fix a crash that startForeground is not called after startForegroundService() call
[email protected]
BUG=826998
(cherry picked from commit c0b4e54e9b2f8ba5b3fa2d9a647c11b1bac67d1b)
Change-Id: Ifcd496ae29831730b1a960478ad42eea8246c2ef
Reviewed-on: https://chromium-review.googlesource.com/1128564
Commit-Queue: Min Qin <[email protected]>
Reviewed-by: Mounir Lamouri <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#574215}
Reviewed-on: https://chromium-review.googlesource.com/1141053
Reviewed-by: Min Qin <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#702}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Video Capture Win] Fallback to DirectShow when MediaFoundation offers no video format
Devices like Pinnacle Dazzle are listed in DirectShow with their video
formats while listed in MediaFoundation with no available video format
at all.
This makes the capture factory fallback to DirectShow implementation
when it contains at least one video format and its MediaFoundation
counterpart has none.
[email protected]
(cherry picked from commit 3772661191b045df5ed2df7aa6fde0a787967fae)
Bug: 862395
Change-Id: I5d02f97971d4cf98372e12bb96c0b7ad9cc6d9c3
Reviewed-on: https://chromium-review.googlesource.com/1137817
Commit-Queue: Christian Fremerey <[email protected]>
Reviewed-by: Christian Fremerey <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#575667}
Reviewed-on: https://chromium-review.googlesource.com/1141051
Cr-Commit-Position: refs/branch-heads/3440@{#701}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
VR: fix autofill popup size
Break SetAlertDialogSize into to methods. One to set the relative
size to the main content, another one to set the absolute size.
Also added comment to hosted_platform_ui to clarify the size of
the rectangle in the model.
Bug: 863071
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: Ie102fcb00865d66052e4bb3c7817831fdcfe5dfa
Reviewed-on: https://chromium-review.googlesource.com/1132140
Reviewed-by: Michael Thiessen <[email protected]>
Commit-Queue: Amirhossein Simjour <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#574688}(cherry picked from commit 9d07f06bb5c43657ce38efc57039e36287eac2a6)
Reviewed-on: https://chromium-review.googlesource.com/1140554
Reviewed-by: Amirhossein Simjour <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#700}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Fix <select> popup width
Fix typo in calculation of AnchoredPopupWindow's width.
Bug: 862594
Change-Id: I0f79ca75c1d3c003d24dcba835fb6925b8d1dab5
Reviewed-on: https://chromium-review.googlesource.com/1136723
Reviewed-by: Bo <[email protected]>
Commit-Queue: Amirhossein Simjour <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#574999}(cherry picked from commit 73221c336f865b79a8738f12f623d11568e28b0f)
Reviewed-on: https://chromium-review.googlesource.com/1140933
Reviewed-by: Amirhossein Simjour <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#699}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Check against null frame_ in GetCanonicalUrlForSharing
Bug: 852350
Change-Id: Ib6c4cc79572d3dad22f663ec61a20bc54f5d7a8f
Reviewed-on: https://chromium-review.googlesource.com/1117847
Commit-Queue: Charlie Reis <[email protected]>
Reviewed-by: Charlie Reis <[email protected]>
Reviewed-by: Daniel Cheng <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#574651}(cherry picked from commit dd341220c263993037559e62938d54d5cf091a2c)
Reviewed-on: https://chromium-review.googlesource.com/1140517
Reviewed-by: Patrick Noland <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#698}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Pwd List] Fix Display Of Passwords
This change fixes a bug when re-rendering the list of passwords after a
password store mutation. This bug could give the impression that a wrong
password was deleted.
Bug: 862119
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I13f42a18567f84e191e99a2beb6d00ee7e82e682
Reviewed-on: https://chromium-review.googlesource.com/1138233
Reviewed-by: Demetrios Papadopoulos <[email protected]>
Commit-Queue: Jan Wilken Dörrie <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#575474}(cherry picked from commit 3f2d86f2d225af1bc3acf4f50c6887c65a5b2678)
Reviewed-on: https://chromium-review.googlesource.com/1140853
Reviewed-by: Jan Wilken Dörrie <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#697}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
More granular UseCounter for document.open()
[email protected]
(cherry picked from commit 136369cac7fc33a14bea3c6650af8ac3bbaf6813)
Bug: 859691
Change-Id: I9f1fbb3dac9b794dcf1f069447096c8559e03d5b
Reviewed-on: https://chromium-review.googlesource.com/1123202
Commit-Queue: Timothy Gu <[email protected]>
Reviewed-by: Yuki Shiino <[email protected]>
Reviewed-by: Hayato Ito <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#572316}
Reviewed-on: https://chromium-review.googlesource.com/1140205
Reviewed-by: Elly Fong-Jones <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#696}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Fix crash: db is null on database failure (M68 merge)
(cherry picked from commit f88ccb0851d0259fec2a4e37d59d0ba3caa1b99d)
Bug: 860228
Change-Id: I8ea5f1f39b8d9a62b5f2a4c608e9a1054d0fb297
Reviewed-on: https://chromium-review.googlesource.com/1129466
Commit-Queue: Dan H <[email protected]>
Reviewed-by: Carlos Knippschild <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#575105}
Reviewed-on: https://chromium-review.googlesource.com/1140736
Cr-Commit-Position: refs/branch-heads/3440@{#695}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Merge to M68: Support beforeunload handlers for OOPIFs.
Currently, when a frame navigates, or a tab closes, we only run
beforeunload handlers in the affected frame, but not in its
cross-process subframes. This can cause data loss in those subframes.
For example, if a subframe contains an editable Google Doc or Office
Online doc with unsaved changes, it uses beforeunload to prompt the
user about losing those changes.
This CL introduces support to dispatch beforeunload handlers to
cross-process subframes. We now dispatch multiple
FrameMsg_BeforeUnload IPCs and wait for all of them to receive
beforeunload ACKs before proceeding with a navigation or tab close.
This is done for browser-initiated navigations, renderer-initiated
navigations, and when closing a tab or browser.
For more details and design discussions, see
https://docs.google.com/document/d/1XmwjGNUl_PF9OgDTs0JsRe0iuGrtEk6mzDYGkkbqHKg/edit#
A few notable tradeoffs and compromises in this initial CL:
- We send one IPC per local root (roughly) and let Blink process
same-site descendants.
- Cross-site beforeunload handlers run in parallel; we only guarantee
ordering among same-site frames. This is similar to how we handle
unload handlers.
- For now, we always send the beforeunload IPC to a navigating frame.
For subframes, we only send it if the subframe has registered a
beforeunload handler.
- Renderer-initiated navigations still execute the navigating frame's
beforeunload before notifying the browser process about the
navigation. The browser process then additionally executes any
cross-site subframe beforeunload handlers, if needed. This avoids
an extra IPC roundtrip.
- beforeunload in window.close() is not yet supported. This is
essentially a renderer-initiated tab close, and it expects to
synchronously set window.closed after executing beforeunload
handlers in all subframes. Supporting this is left to a future CL.
- Blink currently implements an intervention to limit the number of
beforeunload dialogs shown to at most one per navigation. To
support this with OOPIFs, similar support is added on the browser
side in RFHI::OnRunBeforeUnloadConfirm(). More followup work will
be needed here with renderer-initiated navigations and with
recording metrics.
Change-Id: I0b1f86c119a548ee16d34eff229705748f9560be
Bug: 853021
Reviewed-on: https://chromium-review.googlesource.com/1121586
Commit-Queue: Lei Zhang <[email protected]>
Reviewed-by: Charlie Reis <[email protected]>
Reviewed-by: Lei Zhang <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#575133}
Reviewed-on: https://chromium-review.googlesource.com/1137839
Reviewed-by: Alex Moshchuk <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#694}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
sql: Disable very long running ScopedCriticalAction's on iOS.
We are currently marking all critical actions as iOS long running
tasks, even tasks with delays. Because some tasks have long delays,
we always use the maximum 3 minutes before the system suspends us.
This should be reverted once crbug.com/861889 is fixed and delayed
long running tasks are not marked as iOS-critical until they begin
running.
Bug: 861889
Change-Id: I3654ac9b5d94b5d52abef14a79253bd8a9290077
Reviewed-on: https://chromium-review.googlesource.com/1129829
Commit-Queue: Justin Cohen <[email protected]>
Reviewed-by: Rohit Rao <[email protected]>
Reviewed-by: Victor Costan <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#573770}(cherry picked from commit 19ba5438485d0a4abdab60f495921559fcad9e53)
Reviewed-on: https://chromium-review.googlesource.com/1140553
Reviewed-by: Justin Cohen <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#693}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Android WebView] Lower minidump generation fraction to 1% for Stable
To avoid hitting the cap on the number of uploaded crash reports per day
we lower the fraction of uploaded reports from 100% for Beta to 1% for
Stable.
Note that there should be at least one Beta version with the new lowered
fraction since we do not want to re-push Beta just for this change.
Bug: 845111
Change-Id: Id329dd842aaa7b65d29257d54cef8922db84f993
Reviewed-on: https://chromium-review.googlesource.com/1139053
Reviewed-by: Tobias Sargeant <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#692}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Revert "Pass current tab as opener when opening new tab"
This reverts commit 6bdafce48e5663385945c942cb5fbbf5e4edc3f7.
Reason for revert: This CL is breaking the child ordering of tabs creating with Long Press on a link -> Open in a New Tab. They are now opened after the last page opened with ToolsMenu -> Open New Tab. See crbug.com/859508
Original change's description:
> Pass current tab as opener when opening new tab
>
> Pass the current tab as the opener when opening a new tab.
> This allow selection the previous current tab when the
> tab is closed via "pull-to-close" action or via the new
> "close" action in the UI refresh.
>
> The current tab is passed when tab is opened via ([*]
> denotes that this behaviour is added by this CL):
> - open tab in background
> - "New Tab" menu action [*]
> - captive portal detection [*]
> - search by image [*]
>
> Bug: 661988
> Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
> Change-Id: Iecf41a8c0b3cfe465b3ff95a1061c97739b4ed79
> Reviewed-on: https://chromium-review.googlesource.com/1068680
> Reviewed-by: Eugene But <[email protected]>
> Reviewed-by: Mark Cogan <[email protected]>
> Commit-Queue: Sylvain Defresne <[email protected]>
> Cr-Commit-Position: refs/heads/master@{#561427}
[email protected],[email protected],[email protected]
# Not skipping CQ checks because original CL landed > 1 day ago.
Bug: 661988, 859508
Change-Id: I14e6f2350bad216381224aaf3319018e1c1ffdf1
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs
Reviewed-on: https://chromium-review.googlesource.com/1124279
Reviewed-by: Sylvain Defresne <[email protected]>
Commit-Queue: Gauthier Ambard <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#572173}(cherry picked from commit 5cf2911fabed50b4b13f648f3ff7f53c641c895c)
Reviewed-on: https://chromium-review.googlesource.com/1139953
Reviewed-by: Gauthier Ambard <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#691}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Eliminate unnecessary bounds change request
* ClientControlled do not have to have a new bounds when
window is moved to another tree beucase the bounds will
be controlled by a client. (window_positioning_utility.cc)
* Update bounds locally when the window is added to another display.
* Do not move the display if the bounds is set by geometry change.
This scenario isn't important right now and will be fixed by
neww api.
(cherry picked from commit caf225a5b277397876aa62a44eb20effe52681ac)
Bug: 862791, b/110171997
TEST: will be covered by a unit test in a separate CL.
Change-Id: I2be5748661c680fb35bdaa1d25a2bd209edc4a7d
Reviewed-on: https://chromium-review.googlesource.com/1134419
Reviewed-by: Dominik Laskowski <[email protected]>
Commit-Queue: Mitsuru Oshima <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#574737}
Reviewed-on: https://chromium-review.googlesource.com/1139574
Reviewed-by: Mitsuru Oshima <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#690}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.66
[email protected]
Change-Id: I4013603ff16c17af78f405fc5298eaf8255b8a2c
Reviewed-on: https://chromium-review.googlesource.com/1139311
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#689}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Remove not-tablet short circuit in DeviceFormFactor
This patch removes an early return from
DeviceFormFactor#detectScreenWidthBucket that will allow tablets to
return their screen width "bucket". This should prevent tablets from
trying to load phone resources in certain cases.
[email protected]
(cherry picked from commit 126cbe2f37715218e257506cad07091d3261941d)
Bug: 850096
Change-Id: I41868ed5ff582e86b9fb979d1e1a31f215e9d135
Reviewed-on: https://chromium-review.googlesource.com/1125205
Commit-Queue: Matthew Jones <[email protected]>
Reviewed-by: Theresa <[email protected]>
Reviewed-by: agrieve <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#573368}
Reviewed-on: https://chromium-review.googlesource.com/1139077
Reviewed-by: Matthew Jones <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#688}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Merge M68: Update Flash plugin metadata versions to latest version.
https://helpx.adobe.com/security/products/flash-player/apsb18-24.html
BUG=412078
[email protected]
(cherry picked from commit e233c1d178562ac6171d190f1e4d9ec9a94ac11e)
Cq-Include-Trybots: luci.chromium.try:closure_compilation;master.tryserver.chromium.linux:closure_compilation
Change-Id: Iecc32fe539d6d16418086f9d8b4e44fde19bdd69
Reviewed-on: https://chromium-review.googlesource.com/1135713
Commit-Queue: Will Harris <[email protected]>
Reviewed-by: Will Harris <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#574705}
Reviewed-on: https://chromium-review.googlesource.com/1139051
Cr-Commit-Position: refs/branch-heads/3440@{#687}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
arc: bluetooth: Fix a bug where we never send cached device as intended
SendCached.*() never works as our imagination goes.
Cached found devices are always ignored in SendDevices().
Also sends out paired devices in SendCachedDevicesFound(). A paired
device can still have different UUIDs from last time we report to
Android, which should get the latest UUID list as long as it's scanning.
As a matter of fact, the secure client test needs to know the updated
UUIDs on a paired device in order to figure out which one to connect to.
This has an impact on crbug/853037 and crbug/841041 also, as devices are
always paired before connected in BlueZ.
BUG=b:78593133,chromium:853037,chromium:841041
TEST=Confirm from logs that UUIDs are updated even for paired devices
[email protected]
(cherry picked from commit 69e6a7872f1de61abdaee62d873f12a4c8340e6e)
Change-Id: I6f1dae8be9bb1eb9b0d8cb5c2a146ec07d4ee099
Reviewed-on: https://chromium-review.googlesource.com/1105559
Commit-Queue: Qiyu Hu <[email protected]>
Reviewed-by: Luis Hector Chavez <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568505}
Reviewed-on: https://chromium-review.googlesource.com/1138434
Reviewed-by: Miao-chen Chou <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#686}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Adjust frame pixel width in phantom window
Since the width is given in pixels which is correct
only on the display with the same DSF, the width needs to
be multiplied by phanton window scale / source scale.
BUG=861967
TEST=Manual. See bug for repro step.
Change-Id: Ib073bb705d8998cf07f41f9d646f0c23828b48de
Reviewed-on: https://chromium-review.googlesource.com/1130595
Reviewed-by: Jun Mukai <[email protected]>
Commit-Queue: Mitsuru Oshima <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#573550}(cherry picked from commit 4596251cd724b6b2769537558c5fdb3d7f16c413)
Reviewed-on: https://chromium-review.googlesource.com/1138895
Reviewed-by: Mitsuru Oshima <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#685}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Extend SW fallback for VP9 SVC to all platforms.
Initially the fallback was only applied to Windows. But we found
recently that the issue affects ChromeOS as well.
This extends the software fallback to all platforms since we are not
aware about any HW which can reliably decode VP9 SVC.
[email protected]
Bug: 863378
Change-Id: Ie96ffea9f35ae5ce3c1247a1bdf0d6f28f5235c8
Reviewed-on: https://chromium-review.googlesource.com/1133390
Reviewed-by: Sergey Ulanov <[email protected]>
Commit-Queue: Sergey Ulanov <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#574275}(cherry picked from commit 10acfe9a013ab9382993eb4641aaeaad99711bdd)
Reviewed-on: https://chromium-review.googlesource.com/1138833
Cr-Commit-Position: refs/branch-heads/3440@{#684}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Fall back to SW decoding if VP9 SVC is detected.
VP9 DXVA decoders don't have SVC support. They fail to decode high
spatial layers.
Fall back to software decoding if input bitstream has more than one
spatial layer.
[email protected]
Bug: 863378
Change-Id: Ie35ea58afd7b4cf6887f4fa88bb28cf9e59b454d
Reviewed-on: https://chromium-review.googlesource.com/1074694
Reviewed-by: Sergey Ulanov <[email protected]>
Commit-Queue: Sergey Silkin <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#563567}(cherry picked from commit baa63d79ec8713a3c338e7def0dfe5cd594e804a)
Reviewed-on: https://chromium-review.googlesource.com/1137853
Cr-Commit-Position: refs/branch-heads/3440@{#683}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.65
[email protected]
Change-Id: Ib145bfe980d1ccd1c3bb5659ee009c1ee6d8fd26
Reviewed-on: https://chromium-review.googlesource.com/1138755
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#682}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Fix m68 build.
"Don't crash on null peer handler" (9f4ae0a) landed as an unmodified
cherry-pick into m68. Unfortunately, one of the referenced enums changed
from 'enum' to 'enum class' between m68 and m69. This updates m68 to use
the 'enum' which exists in that branch.
Bug: chromium:855161
Change-Id: I9db71ed3398f3364f652ba6f11b50fc0b2bcf44c
Reviewed-on: https://chromium-review.googlesource.com/1138352
Reviewed-by: Ben Wagner <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#681}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Merge to 3440] Add the LSEnvironment variable MallocNanoZone=0.
There appears to be a bug in Launch Services that causes MallocNanoZone=1 to
always be set by default for all applications [this affects applications
launched by Finder, and on restart, but not applications launched from the
Terminal]. I filed https://bugreport.apple.com/web/?problemID=42181038 to track
this.
MallocNanoZone causes libMalloc to use the nano malloc zone by default [affects
allocations <= 256 bytes]. The implementation of nano malloc never frees memory.
See https://bugs.chromium.org/p/chromium/issues/detail?id=861939#c6 for more
details.
This has been observed to cause > 1GB of wasted memory in the browser process.
Possibly a lot more when added up across all processes.
To test this:
1) Build Chrome with patch.
2) Run
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister
-f <path_to_chrome>
3) Launch Chrome from Finder
4) Use "vmmap <pid>" to observe whether there is a MALLOC_NANO summary.
Bug: 861939
Change-Id: I740bcbb006e4ce641d0dde6f6e53dcf4f032ff0b
Reviewed-on: https://chromium-review.googlesource.com/1137131
Reviewed-by: Avi Drissman <[email protected]>
Reviewed-by: Robert Sesek <[email protected]>
Commit-Queue: Erik Chen <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#575108}(cherry picked from commit b32a54d5896276f5f7be79e120e410e1e2537c63)
Reviewed-on: https://chromium-review.googlesource.com/1138294
Reviewed-by: Erik Chen <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#680}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Roll FreeType for m68.
https://chromium.googlesource.com/chromium/src/third_party/freetype2/+log/9e345c911714ed62250be13d03d72e25d91fbc77..62b55f8e51ea8b2b244d8e2ccff5c6aa2170260c
Pick up fuzzer fixes.
BUG=chromium:859303
Change-Id: Ia298dcdf8339e3310b0b64f01c1a3cb180e5d572
Reviewed-on: https://chromium-review.googlesource.com/1138349
Reviewed-by: Ben Wagner <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#679}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Return itself as target if View doesn't have valid InputTargetClient.
When a RenderWidgetHostViewBase doesn't have a valid InputTargetClient
in rare cases on Mac, fallback to early return itself as the target.
Bug: 859492
Change-Id: If473238b947ab2d13512c3ae8d5a818da71584dc
Reviewed-on: https://chromium-review.googlesource.com/1127358
Commit-Queue: Ria Jiang <[email protected]>
Reviewed-by: Ken Buchanan <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#573395}(cherry picked from commit 4670914de3558c1487b86dcbff46c3e6c046e43e)
Reviewed-on: https://chromium-review.googlesource.com/1138517
Reviewed-by: Ria Jiang <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#678}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Updating XTBs based on .GRDs from branch 3440
[email protected]
Change-Id: Ic949dbee7030e656b3ebd34e13a0e13935a3c17b
Reviewed-on: https://chromium-review.googlesource.com/1138536
Reviewed-by: Krishna Govind <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#677}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Merge-M68] [Autofill] Allow crowdsourcing of big forms
This CL increases |kMaxFieldsOnTheForm| to 100 in |FormStructure::IsMalformed|.
It allows to crowdsource more forms. See the bug for details. Later the
parameter will be increased even more and will be finchable.
UMA histogram is introduced to monitor the size of forms Autofill has to process.
TODO: Finch-controlled threshold and UKM metric.
Bug: 857454
Change-Id: I50c1382dd36e2c707cd34f1a4f139413d9ea6026
Reviewed-on: https://chromium-review.googlesource.com/1131457
Reviewed-by: Roger McFarlane <[email protected]>
Reviewed-by: Dominic Battré <[email protected]>
Reviewed-by: Ilya Sherman <[email protected]>
Commit-Queue: Maxim Kolosovskiy <[email protected]>
Cr-Commit-Position: refs/heads/master@{#574150}
Change-Id: Ic53976ddf92e963119909339ec495938820e4abd
Reviewed-on: https://chromium-review.googlesource.com/1137815
Reviewed-by: Maxim Kolosovskiy <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#676}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Don't crash on null peer handler
This is a mitigation of a crash with an unknown cause, which
seems to be causing peer_handler_ to be NULL at an unexpected time.
It returns a rejected promise instead of crashing.
Bug: chromium:855161
Change-Id: Icbb4f42780ae0969ad4d0eff2ef1e9f66a129c11
Reviewed-on: https://chromium-review.googlesource.com/1128972
Commit-Queue: Harald Alvestrand <[email protected]>
Reviewed-by: Guido Urdaneta <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#573462}(cherry picked from commit 6266d795bb329bae876f9568040eee40aa840d0e)
Reviewed-on: https://chromium-review.googlesource.com/1137895
Reviewed-by: Harald Alvestrand <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#675}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.64
[email protected]
Change-Id: I25849d52eb293860506321008c2d3120842496d5
Reviewed-on: https://chromium-review.googlesource.com/1137887
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#674}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.63
[email protected]
Change-Id: I90ab636078079946fc8c878abccc36a0bffe1d5c
Reviewed-on: https://chromium-review.googlesource.com/1137874
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#673}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.62
[email protected]
Change-Id: I45878ebbe2614d88c6687bb7e2a0a59ce3fbafb2
Reviewed-on: https://chromium-review.googlesource.com/1137220
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#672}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
M68: Make the Cloud Print service process listen for WM_QUIT.
The Windows base::MessagePumpUI used to process WM_QUIT, but r553653
changed it to ignore WM_QUIT. This CL adds EnableWmQuit() methods to
MessagePumpForUI and MessageLoopForUI on Windows. The Cloud Print
service process can then call EnableWmQuit() for its MessagePumpForUI
to get the old behavior.
BUG=860827
[email protected]
(cherry picked from commit 23e212e0f9b0d23d39b8958bd44d5b7a0408cb60)
Change-Id: Ie9d9c4c8e2dd205f3ec24cb10be364d0653a7f97
Reviewed-on: https://chromium-review.googlesource.com/1128327
Commit-Queue: Lei Zhang <[email protected]>
Reviewed-by: Wez <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#573620}
Reviewed-on: https://chromium-review.googlesource.com/1137030
Reviewed-by: Lei Zhang <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#671}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Remove CHECK for IPC message queue size
This CHECK was added to diagnose the leaks covered by
https://crbug.com/813045 which are now well understood.
No longer needed.
[email protected], [email protected]
(cherry picked from commit 8984dbc30e230260f717ac1dc02f8774d6f05a2e)
Bug: 826432,813045
Change-Id: I691f4c9a4c4cd9bc5b8823cfae2d9c8bc3cfeabe
Reviewed-on: https://chromium-review.googlesource.com/1124663
Reviewed-by: Ken Rockot <[email protected]>
Commit-Queue: Ken Rockot <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#572259}
Reviewed-on: https://chromium-review.googlesource.com/1136983
Cr-Commit-Position: refs/branch-heads/3440@{#670}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Updating XTBs based on .GRDs from branch 3440
[email protected]
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I47578a87ed2bd4c9a0f9aa4bb22b1dcdf863131d
Reviewed-on: https://chromium-review.googlesource.com/1136894
Reviewed-by: Krishna Govind <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#669}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Fix incorrect return in finally block losing exceptions.
Returning in a finally block causes exceptions to be discarded. There's
no reason to log a UMA stat for the performance of a startup that threw
an exception (since we're going to crash the app anyway), so just take
it entirely outside the finally block and invert the condition to only
record the UMA stat if mFactory.hasStarted().
Also adjust another place that had the same pattern without the "return"
to match, as again there's no need to log the UMA stat when there's an
exception.
[email protected]
(cherry picked from commit 8d96473d6b6ef429cdeeb80ae682e8daa5c74a29)
Bug: 862662
Change-Id: Ie6d24cee5bb9342016c364244256c8b73a8184f7
Reviewed-on: https://chromium-review.googlesource.com/1133332
Commit-Queue: Richard Coles <[email protected]>
Reviewed-by: Tobias Sargeant <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#574941}
Reviewed-on: https://chromium-review.googlesource.com/1136871
Reviewed-by: Richard Coles <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#668}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Remove incorrect DCHECK from WindowPerformance::RegisterEventTiming
Clusterfuzz tells us that GetFrame() could be null when
WindowPerformance::RegisterEventTiming is called, so this CL removes
the DCHECK and bails out early instead.
Bug: 861627
Change-Id: Ic109e8153a80832324d9c3cf27e1bed957d2b1c2
Reviewed-on: https://chromium-review.googlesource.com/1131226
Reviewed-by: Steve Kobes <[email protected]>
Commit-Queue: Nicolás Peña Moreno <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#573769}(cherry picked from commit 3641b5fb4b522a40423e8eaaebdd0150d316f44b)
Reviewed-on: https://chromium-review.googlesource.com/1136752
Reviewed-by: Nicolás Peña Moreno <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#667}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Fix bogus event timestamps across all platforms.
First Input Delay was reporting bogus values in > 0.0006% of cases.
The data suggests that this is due to invalid event timestamps.
Bug: 861855
Change-Id: Ib3e6bb22348546f60dc6b98c6955e8620e87672b
Reviewed-on: https://chromium-review.googlesource.com/1129843
Commit-Queue: Timothy Dresser <[email protected]>
Reviewed-by: Sadrul Chowdhury <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#573878}(cherry picked from commit aacf8c02f2478af54fae69058cfecd846fd95138)
Reviewed-on: https://chromium-review.googlesource.com/1136615
Reviewed-by: Timothy Dresser <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#666}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Media Controls: Keep more overlay play button events in node
This CL undoes some of crrev.com/c/1067514, which kept fewer events in
node for the overlay play button to fix a menu issue. Instead of
allowing all non-play/pause-causing events through, we are only going
to allow non-play/pause-causing "click" events through. This keeps the
original issue fixed while also fixing a new issue where outer divs
could preventDefault on certain touch events to prevent the overlay
play button from receiving a "click" event.
Bug: 858846
Change-Id: I1c10e188529edd1219cee42ded5865442becb8f8
Reviewed-on: https://chromium-review.googlesource.com/1130826
Commit-Queue: Tommy Steimel <[email protected]>
Reviewed-by: Becca Hughes <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#573896}(cherry picked from commit 88dd2a898975364085c5566a30b82a62efd79984)
Reviewed-on: https://chromium-review.googlesource.com/1136751
Reviewed-by: Tommy Steimel <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#665}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[signin] Clear mobile device ID on Sync signout
The device ID was no longer cleared on mobile.
However this is still needed, because it is sent to Sync.
This CL restores the right behavior.
TBR=droger
(cherry picked from commit 7a84e2bf1510ddf73cae1809793bad2e5e5a90cc)
Bug: 855957
Change-Id: Idac22c1ddc2dfa1b8bb68f69051d619b8c8dbe19
Reviewed-on: https://chromium-review.googlesource.com/1129222
Reviewed-by: Mihai Sardarescu <[email protected]>
Commit-Queue: David Roger <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#573670}
Reviewed-on: https://chromium-review.googlesource.com/1136304
Reviewed-by: David Roger <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#664}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[signin] Add device_id parameter to Dice requests
Cherry-picking notes: fixed a broken include in
password_autofill_agent_browsertest.cc.
The device_id is wired-up to Dice, going through ProfileIOData to get
it on the IO thread.
When Sync is enabled, the device ID is cleared on Sync signout.
When Sync is disabled, the device ID is cleared on web signout.
A new device ID is also created immediately when the device ID is
cleared, because it cannot be created lazily on the IO thread.
TBR=droger
(cherry picked from commit 8a009d444d3d980d697e31c3cceb65c5250c27b2)
Bug: 855957
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I4fc6487e16961747899638554c1e496d1dabde2c
Reviewed-on: https://chromium-review.googlesource.com/1115219
Commit-Queue: David Roger <[email protected]>
Reviewed-by: Mihai Sardarescu <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#572950}
Reviewed-on: https://chromium-review.googlesource.com/1136298
Reviewed-by: David Roger <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#663}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Add metrics for the current prefilled usernames fix
crrev.com/c/1007723 introduced a fix to allow the password
manager to recognize some cases when username fields are prefilled with
values that are meant as placeholders and autofill credentials
for those cases.
This CL adds metrics to help assess the effect of that fix.
[email protected]
(cherry picked from commit 609f5d70e6ecb3df0c935cbc3e9ecd2e9519d71c)
Bug: 860161
Change-Id: I4475ed757fc41b4e162b00a7e3b6ab830c496932
Reviewed-on: https://chromium-review.googlesource.com/1122977
Commit-Queue: Ioana Pandele <[email protected]>
Reviewed-by: Robert Kaplow <[email protected]>
Reviewed-by: Vadym Doroshenko <[email protected]>
Reviewed-by: Dominic Battré <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#573667}
Reviewed-on: https://chromium-review.googlesource.com/1136043
Cr-Commit-Position: refs/branch-heads/3440@{#662}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.61
[email protected]
Change-Id: I3933c82da72204fcf0e7284ac1e1fb1dd03f7137
Reviewed-on: https://chromium-review.googlesource.com/1136014
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#661}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Image Capture, Android] Fix for "UnknownError: platform error"
Fixes an issue where takePhoto would occasionally fail due to a Java object
being released too early.
In particular, an ImageReader instance is created and its Surface object is
held on to and used asynchronously while the ImageReader goes out of scope and
may get garbage collected. The fix is to hold on to the ImageReader instance
for as long as the Surface may be used.
Bug: 846576
Change-Id: Icb0e3b247a1a75af8ce86c44774960c2b036083b
Reviewed-on: https://chromium-review.googlesource.com/1117854
Reviewed-by: Emircan Uysaler <[email protected]>
Commit-Queue: Christian Fremerey <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#571574}(cherry picked from commit 356a67ed5facf20d6a52748444bb580fe73dc329)
Reviewed-on: https://chromium-review.googlesource.com/1135353
Reviewed-by: Christian Fremerey <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#660}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Image Capture, Android] Fix for "Check failed: false. |callback_id| not found"
Fixes a race condition that can lead to a crash when taking a photo via the
image capture web API on Android.
Bug: 846576
Change-Id: I0008391acfd4fd1f84db1d403d33c0dc31410294
Reviewed-on: https://chromium-review.googlesource.com/1117845
Reviewed-by: Emircan Uysaler <[email protected]>
Commit-Queue: Christian Fremerey <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#571538}(cherry picked from commit 5481b4c6fa6dcbddca13d3f67175f651c1e75b33)
Reviewed-on: https://chromium-review.googlesource.com/1135352
Reviewed-by: Christian Fremerey <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#659}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Pass variation headers for Omnibox Searches.
Variation headers will only be added to URL requests to Google servers.
Variation headers will be passed for the following navigations:
- Text search from the Omnibox
- Back-forward navigation to search pages loaded from omnibox text search
- Reload of the search page
Headers will *not* be passed for the following navigations:
- QR code scanner search
- Voice Search
- Bookmarks
- Search by image
- NTP tiles and articles
- History navigations
- Learn More on Incognito
- Recent Tab navigation
- Reading List article load
[email protected]
(cherry picked from commit 1ce01901eba7a11541dc1a7eac0aa6fd70ac953d)
Bug: 831976
Change-Id: I0c0c1f46592003c21f0fc11eacfd16767a864477
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Reviewed-on: https://chromium-review.googlesource.com/1069335
Reviewed-by: Stepan Khapugin <[email protected]>
Reviewed-by: Peter Lee <[email protected]>
Commit-Queue: Eugene But <[email protected]>
Cr-Original-Original-Commit-Position: refs/heads/master@{#563386}
Reviewed-on: https://chromium-review.googlesource.com/1131690
Reviewed-by: Eugene But <[email protected]>
Cr-Original-Commit-Position: refs/branch-heads/3440@{#632}
Cr-Original-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Reviewed-on: https://chromium-review.googlesource.com/1135436
Reviewed-by: Kariah Davis <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#658}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Updating XTBs based on .GRDs from branch 3440
[email protected]
Change-Id: I7876b1895971c086ad25fc4c77243f8464db76d7
Reviewed-on: https://chromium-review.googlesource.com/1135576
Reviewed-by: Krishna Govind <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#657}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Fix Android B&R and GLS check boxes for consumers
We changed the enterprise/edu default so that unless the corresponding
policies are explicitly set to "let the user decide," Android B&R and
GLS are disabled and the corresponding check boxes are grayed out.
Unfortunately, the policy handler code that implements this logic runs
for consumer users as well. Consumers have no policies set, so the new
default behavior kicks in, disabling and graying out the Android B&R
and GLS check boxes.
This CL fixes consumer behavior by only controlling B&R and GLS if the
ArcEnabled policy is set. Since this policy is unset for consumers, they
are shielded from the new behavior. Some enterprise users may also have
the policy unset, but ArcEnabled unset or false for enterprise users
means ARC++ is disabled, so B&R and GLS are N/A anyway.
[email protected]
(cherry picked from commit 0248c495fd24353a1e9feba0981fddd554a7ac08)
Bug: 849867
Test: ArcServicePolicyHandlerTest and manual verification
Change-Id: Id3b785e4cde02716d54391607a64fac58604ed88
Reviewed-on: https://chromium-review.googlesource.com/1120177
Commit-Queue: Bartosz Fabianowski <[email protected]>
Reviewed-by: Maksim Ivanov <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#571879}
Reviewed-on: https://chromium-review.googlesource.com/1134483
Reviewed-by: Josh Horwich <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#656}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Do not skip chrome sign-in form in the renderer process.
Chrome sign-in passwords shouldn't be saved, so Chrome sign-in form
sholdn't be skipped. On CL
https://chromium-review.googlesource.com/c/chromium/src/+/979932 it was
implemented skipping this form in the renderer process. As result
password hash can't be saved. This CL implements skipping such form
in the browser process. As positive side effects, it adds checking
whether to save a password in ShowManualFallbackForSaving, that
avoids to show manual fallback for sync credentials for any form.
Bug:852205
[email protected]
(cherry picked from commit 7a9340678c5ceb4c06abc270beea92aa0c999957)
Change-Id: I4d749aecdb57dab03b7928f551f41c015490da56
Reviewed-on: https://chromium-review.googlesource.com/1120342
Commit-Queue: Vadym Doroshenko <[email protected]>
Reviewed-by: Mike West <[email protected]>
Reviewed-by: Vasilii Sukhanov <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#572585}
Reviewed-on: https://chromium-review.googlesource.com/1135309
Reviewed-by: Vadym Doroshenko <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#655}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Revert "Pass variation headers for Omnibox Searches."
This reverts commit f0f24f13f01c9ac3ed6ef4045537d3ac785ae77f.
Reason for revert: Breaks beta compilation
Original change's description:
> Pass variation headers for Omnibox Searches.
>
> Variation headers will only be added to URL requests to Google servers.
>
> Variation headers will be passed for the following navigations:
> - Text search from the Omnibox
> - Back-forward navigation to search pages loaded from omnibox text search
> - Reload of the search page
>
> Headers will *not* be passed for the following navigations:
> - QR code scanner search
> - Voice Search
> - Bookmarks
> - Search by image
> - NTP tiles and articles
> - History navigations
> - Learn More on Incognito
> - Recent Tab navigation
> - Reading List article load
>
> [email protected]
>
> (cherry picked from commit 1ce01901eba7a11541dc1a7eac0aa6fd70ac953d)
>
> Bug: 831976
> Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
> Change-Id: I28be85db0a38b64f933d0b57746b474aeecbf546
> Reviewed-on: https://chromium-review.googlesource.com/1069335
> Reviewed-by: Stepan Khapugin <[email protected]>
> Reviewed-by: Peter Lee <[email protected]>
> Commit-Queue: Eugene But <[email protected]>
> Cr-Original-Commit-Position: refs/heads/master@{#563386}
> Reviewed-on: https://chromium-review.googlesource.com/1131690
> Reviewed-by: Eugene But <[email protected]>
> Cr-Commit-Position: refs/branch-heads/3440@{#632}
> Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[email protected],[email protected],[email protected]
# Not skipping CQ checks because original CL landed > 1 day ago.
Bug: 831976
Change-Id: Iddbd4d578cfae45706b214e5de2ff9f4ffe2efaa
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Reviewed-on: https://chromium-review.googlesource.com/1134786
Reviewed-by: Olivier Robin <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#654}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Migrate Services Data Use to Traffic Annotations
Network traffic annotations provides an unique hash for each component that
creates the URLRequest. This CL records data use against the hashes, so that
no client change is needed when new services are added. New service names
could be independently added in enums.xml.
Different conditions upstream/downstream, app state in background/foreground
are added as suffixes to the histogram. Notably, network connection type
(cellular/non-cellular) is not added as suffix.
This CL also deprecates the histograms DataUse.AllServices.BackgroundKB
and DataUse.MessageSize.AllServices.* histograms.
[email protected]
(cherry picked from commit a0242d8885e006ee2daa4663802114af0002eab1)
Bug: 843715
Change-Id: Iecffb840afa1880bd383972c30e82925b519c18b
Reviewed-on: https://chromium-review.googlesource.com/1114061
Reviewed-by: Robert Kaplow <[email protected]>
Reviewed-by: Ramin Halavati <[email protected]>
Reviewed-by: Eric Roman <[email protected]>
Reviewed-by: Ryan Sturm <[email protected]>
Commit-Queue: rajendrant <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#571754}
Reviewed-on: https://chromium-review.googlesource.com/1134727
Reviewed-by: rajendrant <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#653}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Do not optimize base::debug::Alias().
Optimization is already disabled for MSVC, do the same thing for Clang
too.
BUG=861636
TEST=Run dump_syms against chrome (w/ symbol_level=3, use_thin_lto=true,
use_lld=true) and manually checked the output.
Change-Id: Ia275e2310ccb8e70a2392d95ca4acadf2f218b01
Reviewed-on: https://chromium-review.googlesource.com/1128693
Reviewed-by: Lei Zhang <[email protected]>
Commit-Queue: Lei Zhang <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#573365}(cherry picked from commit a31f26075580e73b05da1bb1d899b5edec38cea8)
Reviewed-on: https://chromium-review.googlesource.com/1134607
Reviewed-by: Ryo Hashimoto <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#652}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.60
[email protected]
Change-Id: I4edf9c19c79a908c28259c16b8f5101535565b81
Reviewed-on: https://chromium-review.googlesource.com/1134214
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#651}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Updating XTBs based on .GRDs from branch 3440
[email protected]
Change-Id: Id75bbcc2e46e5f12ec5866df450942e099f04f39
Reviewed-on: https://chromium-review.googlesource.com/1134501
Reviewed-by: Krishna Govind <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#650}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Merge to M68: Android accessibility: skip the root element when it has no title
This change was originally landed in r432621 - the idea is that when a page
has no title, there's no reason we should allow the user to swipe to the
root element.
For some reason in r514252 this was inverted as part of making it possible
to jump to the last element on a page, but the new logic doesn't make
sense. Restore it to the previous behavior.
Bug: 661793, 660090, 801292
Change-Id: Iba81d0429a04845f093c5f07449c26fa8514bda4
Reviewed-on: https://chromium-review.googlesource.com/1097953
Reviewed-by: Alice Boxhall <[email protected]>
Commit-Queue: Dominic Mazzoni <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#566868}(cherry picked from commit a953ec895d88d23a76772b9ff5cce1a4a84348c8)
Reviewed-on: https://chromium-review.googlesource.com/1134101
Reviewed-by: Dominic Mazzoni <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#649}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
This cl merges https://chromium-review.googlesource.com/1112776 to m68.
I manually cherry picked 4b32e5d123858b92e02524bff9a3ecc16ccd692e
and compiled locally after resolving the merge conflict in
GestureListenerManagerImpl.java
[email protected],[email protected],[email protected]
Change-Id: Icb74a6fac4577cf7e071d612c6a503479d845244
Reviewed-on: https://chromium-review.googlesource.com/1134192
Reviewed-by: Avi Drissman <[email protected]>
Reviewed-by: Bo <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#648}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Download location: Fix ANR issue.
Currently download location feature may access disk on main thread to
retrieve download directories.
This CL moves this operation to a background thread.
Also, the Android API to retrieve directories may cause issue if
multiple asynchrounous tasks are fired on certain device. In this CL,
we introduced a glue layer between Android API and chrome to manage
unreliable API behavior.
[email protected]
(cherry picked from commit 6bd45c89d07e02baf433f24a53aba83efae05a74)
Bug: 844107
Change-Id: Ic9dcabea48895a705079029f9fa260ce6efbfec3
Reviewed-on: https://chromium-review.googlesource.com/1116247
Commit-Queue: Xing Liu <[email protected]>
Reviewed-by: David Trainor <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#571371}
Reviewed-on: https://chromium-review.googlesource.com/1134082
Reviewed-by: Xing Liu <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#647}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Merge M68] Android process binding fixes
* Add back boostForPendingView logic accidentally removed in r554797
* Send updates when frame depth changes, which was missing in r546622.
Note this fix is limited to OS_ANDROID to maintain the desktop
workaround for crbug.com/560446
* Also improve testCrossDomainNavigationDoNotLoseImportance to also
log the calling stack on failure.
(cherry picked from commit 07fe724b57d94ce25bbb520410e5b596f856d826)
Bug: 861826
Change-Id: I0757647a81228a9bfc5fda02d775f62fb6bee723
Reviewed-on: https://chromium-review.googlesource.com/1128573
Reviewed-by: Charlie Reis <[email protected]>
Reviewed-by: Yaron Friedman <[email protected]>
Commit-Queue: Bo <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#573540}
Reviewed-on: https://chromium-review.googlesource.com/1133777
Reviewed-by: Bo <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#646}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
VR: fix rendering of permission popups in presentation mode
Bug: 856727
Change-Id: Ic1cdbe5a46f5c559713f29a217243a30347eeb89
Reviewed-on: https://chromium-review.googlesource.com/1127147
Commit-Queue: Aldo Culquicondor <[email protected]>
Reviewed-by: Amirhossein Simjour <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#572820}(cherry picked from commit 10380658b5506f3251d989186f18ab904e8bb9ec)
Reviewed-on: https://chromium-review.googlesource.com/1132325
Cr-Commit-Position: refs/branch-heads/3440@{#645}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.59
[email protected]
Change-Id: I7260fcde941e2fd7fbcb4eddf7e7617203b7aa16
Reviewed-on: https://chromium-review.googlesource.com/1132403
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#644}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Don't throw away bits when computing Blink heap magic.
Bug: 860721
Change-Id: I8d32e43efa102d257360c2886aa1701298e3c91e
Reviewed-on: https://chromium-review.googlesource.com/1132082
Reviewed-by: Kentaro Hara <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#643}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.58
[email protected]
Change-Id: Ia0f8418372bc232b9ceef9932715794a103e077f
Reviewed-on: https://chromium-review.googlesource.com/1132397
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#642}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
arc: Make SET_REPORTING_CONSENT false for managed users
Keep usage & diagnostics false during ARC setup if the user does not
see the ARC ToS dialog due to all relevant settings being managed,
even if usage & diagnostics is enabled for the device.
Note that this is a squashed patch of the following three commits:
commit 25a10afd2e5303a00b5f19d2cdd1b5a735723e44
commit c59e0e374abf33db3b17cd269be347a200e7ed64
commit 7da098a199b64a48665d57352e390acc48bfc09d
Bug: b/73338614, 859104, 855448
Test: Opt in to ARC with managed and unmanaged users
Change-Id: I5fbe412d8cd7e3e0ca0ee77c325ba0903e677414
Signed-off-by: Josh Horwich <[email protected]>
Reviewed-on: https://chromium-review.googlesource.com/1121212
Reviewed-by: Long Cheng <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#641}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Record UKMs if a manual save fallback is offered to the user
This CL introduce a UKM metric that tells us if a manual fallback for password
saving was offered, which means that the user typed a not yet stored credential
into a password form. The purpose of this is to see whether we see such sites
where manual fallback is offered but form submissions are not observed.
[email protected]
(cherry picked from commit 061f70757acaab80075714aaa2f93c532e26c38c)
Bug: 732846
Change-Id: If2bce7b0e7219f84880110218b8ea6d1d955c165
Reviewed-on: https://chromium-review.googlesource.com/1126932
Reviewed-by: Robert Kaplow <[email protected]>
Reviewed-by: Vadym Doroshenko <[email protected]>
Commit-Queue: Dominic Battré <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#572797}
Reviewed-on: https://chromium-review.googlesource.com/1131940
Reviewed-by: Dominic Battré <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#640}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Fix DCHECK in WebFormElementObserverImpl
The WebFormElementObserverImpl made an incorrect but also totally unnecessary
cast of a Node to an HTMLElement. This edge case was discovered by the fuzzer
where a form was inside an <svg> element, whose style attribute was changed,
but which could not be casted to HTMLElement.
[email protected]
(cherry picked from commit 5ce8880baa741c8e31cfd47ede17490128590488)
Bug: 861571
Change-Id: I62c8238e25ef39e662dc154a1f2bd772667ec52f
Reviewed-on: https://chromium-review.googlesource.com/1128973
Reviewed-by: Jochen Eisinger <[email protected]>
Commit-Queue: Dominic Battré <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#573458}
Reviewed-on: https://chromium-review.googlesource.com/1131939
Reviewed-by: Dominic Battré <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#639}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[M68] Disable cold mode spellchecker
Cold mode spellchecker was introduced in M68 as a bug fix to some
spellcheck completeness issues. For risk control, it is implemented
behind a flag.
Now that we found many related crashes in M68 and M69, it turns out
that cold mode spellchecker is not ready to be pushed to the stable
channel. Hence, this patch disables it by default on M68.
It will remain enabled by default in M69 for more observation.
Bug: 716642, 856376, 859056, 859443
Change-Id: I8984de679d0c7c0de61123f50dabc535b2b3c3fb
Reviewed-on: https://chromium-review.googlesource.com/1124021
Reviewed-by: Kent Tamura <[email protected]>
Reviewed-by: Yoshifumi Inoue <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#638}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Updating XTBs based on .GRDs from branch 3440
[email protected]
Change-Id: I83d783bf54312c713855925e35dcc7d1af9e931e
Reviewed-on: https://chromium-review.googlesource.com/1131930
Reviewed-by: Krishna Govind <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#637}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Merge to 3440] Fix re-entrancy caused by RenderFrameHostImpl::DispatchBeforeUnload.
The method, on certain conditions, would simulate receiving a
OnBeforeUnloadACK() IPC. This would immediately call back into the unload
handler, which had just called RenderFrameHostImpl::DispatchBeforeUnload.
The problematic series of events is as follows:
1) TabStripModel::CloseWebContentses tries to close many tabs.
2) This calls RunUnloadListenerBeforeClosing() on each tab.
3) UnloadListener will call RenderFrameHostImpl::DispatchBeforeUnload, which
on certain conditions will synchronously call OnBeforeUnloadACK().
4) This calls back into TabStripModel, mutating internal state.
5) The implementation of TabStripModel::CloseWebContentses relies on the
assumption that there is no re-entrancy. This manifests itself as a buffer
overrun when (1) calls SendDetachWebContentsNotifications, which then
passes inconsistent data to the observers.
Bug: 851400
Change-Id: I2080875f5d8d118c93addbe66503cb02b8b2966f
Reviewed-on: https://chromium-review.googlesource.com/1101846
Commit-Queue: Erik Chen <[email protected]>
Reviewed-by: Charlie Reis <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568534}(cherry picked from commit 907fe4acf7dc713ed05e1608663444b2278de1f6)
Reviewed-on: https://chromium-review.googlesource.com/1129400
Reviewed-by: Erik Chen <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#636}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Fix feature policy construction in proxies.
When a proxy for a newly-created frame is created in an existing
renderer, the Feature-Policy header and container policy need to be
applied after the origin is set. Previously, setting the proxy's origin
(as the last step in frame navigation) would reuse the feature policy
which was created during frame initialization without taking into
account either the HTTP header or the new origin's relationship to the
parent frame.
This CL ensures that the remote frame stores a copy of the initial
feature policy header, which it can use to reconstruct the correct
policy when the origin is set. The
FeaturePolicy::CreateFromPolicyWithOrigin method, which was used to
replicate an existing policy with an updated origin, is removed, as it
appears to never be the right behaviour.
[email protected]
(cherry picked from commit bd2a91ac57dcfe16ce53877c776843a6cf1f8216)
Bug: 852102
Change-Id: I3e5137737a5aac102f247aa52ede842f1210f53f
Reviewed-on: https://chromium-review.googlesource.com/1124931
Reviewed-by: Daniel Cheng <[email protected]>
Reviewed-by: Alex Moshchuk <[email protected]>
Commit-Queue: Ian Clelland <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#573149}
Reviewed-on: https://chromium-review.googlesource.com/1131926
Reviewed-by: Ian Clelland <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#635}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Merge of DevTools: restore pointer events in HTML preview
- Restores pointer events (including scrolling) to HTML preview.
- Prevents accidentally focusing inputs/links inside the preview
iframe when tabbing via keyboard.
Bug: 849204
Change-Id: Iea5dc6117decbe1d9e746139dd5974a8bfb45c62
Reviewed-on: https://chromium-review.googlesource.com/1107250
Reviewed-by: Dmitry Gozman <[email protected]>
Commit-Queue: Erik Luo <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#569093}(cherry picked from commit 122037b2541bf0932fd6fbcb29a98d487525c4ec)
Reviewed-on: https://chromium-review.googlesource.com/1132014
Reviewed-by: Erik Luo <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#634}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Mac merge into M68] Merge 2 CLs into M68 and resolve conflict
[Mac] Collect detached code signatures when analyzing DMG files.
A detached signature is created by codesign(1) when the signed artifact
is not Mach-O, so the resulting signature cannot be placed in the
LC_CODE_SIGNATURE command. Instead, the signature is detached into the
_CodeSignature/CodeSignature file on-disk.
This also updates the testing codesign certificate used for the
safe_browsing/mach_o test data, since new test data needed to be generated.
The existing test data were not re-signed with it, however.
Bug: 826761
Change-Id: Ied0e96b3b0079b86679724b08aa46bf8d2669a94
Reviewed-on: https://chromium-review.googlesource.com/1101842
Reviewed-by: Ken Rockot <[email protected]>
Reviewed-by: Gayane Petrosyan <[email protected]>
Reviewed-by: Varun Khaneja <[email protected]>
Reviewed-by: Jialiu Lin <[email protected]>
Commit-Queue: Robert Sesek <[email protected]>
Cr-Commit-Position: refs/heads/master@{#569101}
[Mac] Fix crash in safe_browsing::dmg::AnalayzeDMGFile()
This could occur if a detached code signature file is shorter than its
typical prologue.
Bug: 826761
Test: unit_tests --gtest_filter=DMGAnalyzerTest.InvalidDetachedCodeSignature
Change-Id: Ic11b12eb9ce7d7b787b7668af43e2c6ddb3abd52
Reviewed-on: https://chromium-review.googlesource.com/1114925
Commit-Queue: Robert Sesek <[email protected]>
Reviewed-by: Jialiu Lin <[email protected]>
Cr-Commit-Position: refs/heads/master@{#570530}
(cherry picked from commit b899c92d17aeeb7d002d555558eb8fffd0177ce5)
[email protected], [email protected], [email protected]
Bug: 826761
Change-Id: Ie33179f80ca0de57ed3383d2c3de0a0a3385efc6
Reviewed-on: https://chromium-review.googlesource.com/1131717
Reviewed-by: Jialiu Lin <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#633}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Pass variation headers for Omnibox Searches.
Variation headers will only be added to URL requests to Google servers.
Variation headers will be passed for the following navigations:
- Text search from the Omnibox
- Back-forward navigation to search pages loaded from omnibox text search
- Reload of the search page
Headers will *not* be passed for the following navigations:
- QR code scanner search
- Voice Search
- Bookmarks
- Search by image
- NTP tiles and articles
- History navigations
- Learn More on Incognito
- Recent Tab navigation
- Reading List article load
[email protected]
(cherry picked from commit 1ce01901eba7a11541dc1a7eac0aa6fd70ac953d)
Bug: 831976
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I28be85db0a38b64f933d0b57746b474aeecbf546
Reviewed-on: https://chromium-review.googlesource.com/1069335
Reviewed-by: Stepan Khapugin <[email protected]>
Reviewed-by: Peter Lee <[email protected]>
Commit-Queue: Eugene But <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#563386}
Reviewed-on: https://chromium-review.googlesource.com/1131690
Reviewed-by: Eugene But <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#632}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Updating XTBs based on .GRDs from branch 3440
[email protected]
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.linux:closure_compilation;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I860b7606174179866afb673c6d3d2bc101a9f33f
Reviewed-on: https://chromium-review.googlesource.com/1131534
Reviewed-by: Krishna Govind <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#631}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[signin] Re-use existing signin tabs
Previously, each sign-in request was processed in a new tab.
This was a problem because a mis-behaving extension could make many
signin request, and trigger the creation of many new tabs.
This CL mitigates the bug by reusing an existing signin tab if available.
Note that this does not completely address the problem, because the
signin tab is given the focus, and thus a misbehaving extension is still
able to constantly bring a signin tab into focus, as well as constantly
reopening the signin tab when it is closed.
[email protected]
(cherry picked from commit cd0d663fee8a8506e94f2849b8b82d096601dcf3)
Bug: 856513
Change-Id: I077054857c311a319408d63dfc2bdf56567c4f11
Reviewed-on: https://chromium-review.googlesource.com/1124691
Reviewed-by: Mihai Sardarescu <[email protected]>
Commit-Queue: David Roger <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#572802}
Reviewed-on: https://chromium-review.googlesource.com/1131118
Reviewed-by: David Roger <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#630}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Merge "custom-element: Do not crash by Get(NewTarget, "prototype") failure." to M68 branch
https://html.spec.whatwg.org/multipage/dom.html#html-element-constructors
> 7. Let prototype be Get(NewTarget, "prototype"). Rethrow any exceptions.
As the specification says, we should rethrow. Removing a v8::TryCatch
instance in V8HTMLConstructor::HtmlConstructor() works as "rethrow".
Bug: 854887
Change-Id: I6b2d6ae829453270fe4437a87e65528525c64990
Reviewed-on: https://chromium-review.googlesource.com/1124129
Reviewed-by: Yuki Shiino <[email protected]>
Reviewed-by: Kentaro Hara <[email protected]>
Reviewed-by: Hitoshi Yoshida <[email protected]>
Commit-Queue: Kent Tamura <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#572167}(cherry picked from commit 8381e35ca626c9853c6207de30828b7c3039430c)
Reviewed-on: https://chromium-review.googlesource.com/1130576
Reviewed-by: Kent Tamura <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#629}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Revert Ozone initialization changes.
This reverts most of commit a51e3935c81c5572eb1439a1f8d83c9184f3f128.
The thread configuration for --enable-features=Mus doesn't exist anymore
and fixing mus introduced a different race for the non-mus configuration.
Since mus is no longer the plan of record, revert the initialization
order changes but keep logging and code cleanup.
Bug: 840474
Change-Id: Ifec0e3dd9601e3895d0549109be5d10387f3b8b4
Reviewed-on: https://chromium-review.googlesource.com/1101139
Reviewed-by: Robert Kroeger <[email protected]>
Commit-Queue: kylechar <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#567794}(cherry picked from commit b33fd39c100223d0d8aecdec3308228b41642514)
Reviewed-on: https://chromium-review.googlesource.com/1130854
Reviewed-by: kylechar <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#628}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.57
[email protected]
Change-Id: I2444369579f8efae0d7e2bc027de6e2b8a1ae46a
Reviewed-on: https://chromium-review.googlesource.com/1130696
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#627}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Reland: "Download: Fix an issue that download percentage can move backwards."
On certain Android devices, when disconnecting from WIFI, the network
code will report NETWORK_TIMEOUT before NETWORK_DISCONNECT and trigger
auto download resumption. And we erase the data downloaded by parallel
requests, so the download percentage will go backwards.
Instead, we should keep the slice info when resume with an error.
[email protected], [email protected], [email protected]
(cherry picked from commit 1dba58736239a49120531e98631010925aaafffa)
Bug: 837128
Change-Id: I59ddb7ff57551beb862884febe2de3f3ee9e1359
Reviewed-on: https://chromium-review.googlesource.com/1130349
Reviewed-by: Xing Liu <[email protected]>
Commit-Queue: Xing Liu <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#573547}
Reviewed-on: https://chromium-review.googlesource.com/1130816
Cr-Commit-Position: refs/branch-heads/3440@{#626}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[M68] Replace MtpManager's ReadDirectory() with ReadDirectoryEntryIds().
[email protected]
BUG=858899
Replace MtpManager's ReadDirectory() with ReadDirectoryEntryIds().
MediaTransferProtocolDaemonClient currently provides a low-level
ReadDirectoryEntryIds() method, and MtpManager does the translation to
the high-level ReadDirectory() method that MTPDeviceTaskHelper
understands.
Change MtpManager's ReadDirectory() method to ReadDirectoryEntryIds(),
so it acts more like a pass-through. Make MTPDeviceTaskHelper handle the
translation.
BUG=769630
Change-Id: I5154bd4beac0b6ab15579f166cdf8b8add6a7dac
Reviewed-on: https://chromium-review.googlesource.com/1080214
Commit-Queue: Lei Zhang <[email protected]>
Reviewed-by: Colin Blundell <[email protected]>
Reviewed-by: Tom Sepez <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#565441}(cherry picked from commit 44663e8f02729bf01d296ce86087f87168420713)
Reviewed-on: https://chromium-review.googlesource.com/1130735
Reviewed-by: Anand Mistry <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#625}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[M68] Align GetFileInfo() between MtpManager and MtpDaemonClient.
[email protected]
BUG=858899
Align GetFileInfo() between MtpManager and MtpDaemonClient.
MediaTransferProtocolDaemonClient currently provides a low-level
GetFileInfo() method, and MtpManager does the translation to the
high-level GetFileInfo() method that MTPDeviceTaskHelper understands.
Change MtpManager's GetFileInfo() from the high-level method to the
low-level method, so it acts more like a pass-through. Make
MTPDeviceTaskHelper handle the translation.
BUG=769630
Change-Id: I21e20b71d333a1ee7173071f04aaf2e37dd61844
Reviewed-on: https://chromium-review.googlesource.com/1080212
Commit-Queue: Lei Zhang <[email protected]>
Reviewed-by: Tom Sepez <[email protected]>
Reviewed-by: Colin Blundell <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#565413}(cherry picked from commit 3d7f15c742e7aff293b9b2065837bf98cb3a042b)
Reviewed-on: https://chromium-review.googlesource.com/1130715
Reviewed-by: Anand Mistry <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#624}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Weaken a precondition for client_ in DocumentThreadableLoader destructor
Having a non-null client_ in DocumentThreadableLoader destructor
generally means UaF, so we have a CHECK there.
In the detached case, the loader is held by self-referencing
DetachedClient, but SelfKeepAlive in DetachedClient is forcibly
cancelled on worker thread termination. This is a safe pattern, so we
should ignore this case.
[email protected]
(cherry picked from commit 8ec0126d926388c03016100db87d1dd3454fdf34)
Bug: 837511
Change-Id: I451ccddc0f72c2b0d0ec05c707b983e18547feae
Reviewed-on: https://chromium-review.googlesource.com/1127509
Commit-Queue: Yutaka Hirano <[email protected]>
Reviewed-by: Adam Rice <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#572959}
Reviewed-on: https://chromium-review.googlesource.com/1130555
Reviewed-by: Yutaka Hirano <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#623}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Revert "[Mac merge M68] Collect detached code signatures when analyzing DMG files."
This reverts commit 5cfa9fabbdba23376ff7d8776d3f0b735c80e728.
Reason for revert: breaking continuous build due to merge conflicts
Original change's description:
> [Mac merge M68] Collect detached code signatures when analyzing DMG files.
>
> A detached signature is created by codesign(1) when the signed artifact
> is not Mach-O, so the resulting signature cannot be placed in the
> LC_CODE_SIGNATURE command. Instead, the signature is detached into the
> _CodeSignature/CodeSignature file on-disk.
>
> This also updates the testing codesign certificate used for the
> safe_browsing/mach_o test data, since new test data needed to be generated.
> The existing test data were not re-signed with it, however.
>
> [email protected]
>
> (cherry picked from commit 0b82d4cd3484d173e7f1ec20a0de062663a20d06)
>
> Bug: 826761
> Change-Id: Ied0e96b3b0079b86679724b08aa46bf8d2669a94
> Reviewed-on: https://chromium-review.googlesource.com/1101842
> Reviewed-by: Ken Rockot <[email protected]>
> Reviewed-by: Gayane Petrosyan <[email protected]>
> Reviewed-by: Varun Khaneja <[email protected]>
> Reviewed-by: Jialiu Lin <[email protected]>
> Commit-Queue: Robert Sesek <[email protected]>
> Cr-Original-Commit-Position: refs/heads/master@{#569101}
> Reviewed-on: https://chromium-review.googlesource.com/1129551
> Cr-Commit-Position: refs/branch-heads/3440@{#617}
> Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[email protected],[email protected],[email protected],[email protected],[email protected]
Change-Id: Ibc7eee944f549df3d8138796a507d9074e5a4401
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 826761
Reviewed-on: https://chromium-review.googlesource.com/1130139
Reviewed-by: Jialiu Lin <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#622}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Revert "[Mac merge M68] Fix crash in safe_browsing::dmg::AnalayzeDMGFile()"
This reverts commit aa78d07711cb1d94bf0bf9c098662babc0a10a86.
Reason for revert: breaking build because of merge conflict
Original change's description:
> [Mac merge M68] Fix crash in safe_browsing::dmg::AnalayzeDMGFile()
>
> This could occur if a detached code signature file is shorter than its
> typical prologue.
>
> [email protected]
>
> (cherry picked from commit b899c92d17aeeb7d002d555558eb8fffd0177ce5)
>
> Bug: 826761
> Test: unit_tests --gtest_filter=DMGAnalyzerTest.InvalidDetachedCodeSignature
> Change-Id: Ic11b12eb9ce7d7b787b7668af43e2c6ddb3abd52
> Reviewed-on: https://chromium-review.googlesource.com/1114925
> Commit-Queue: Robert Sesek <[email protected]>
> Reviewed-by: Jialiu Lin <[email protected]>
> Cr-Original-Commit-Position: refs/heads/master@{#570530}
> Reviewed-on: https://chromium-review.googlesource.com/1129552
> Cr-Commit-Position: refs/branch-heads/3440@{#618}
> Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[email protected],[email protected]
Change-Id: Ib92f5384942ca257ab98c6f3cfb010cc2afe6860
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 826761
Reviewed-on: https://chromium-review.googlesource.com/1130119
Reviewed-by: Jialiu Lin <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#621}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Revert "Download: Fix an issue that download percentage can move backwards."
This reverts commit 1917d9a9ab35eadaa2ddb37932224159567cd110.
Reason for revert: Some testing function is modified, so I need to revert this CL,
and then revert the one on trunk, then checking in a new one without the test.
Original change's description:
> Download: Fix an issue that download percentage can move backwards.
>
> On certain Android devices, when disconnecting from WIFI, the network
> code will report NETWORK_TIMEOUT before NETWORK_DISCONNECT and trigger
> auto download resumption. And we erase the data downloaded by parallel
> requests, so the download percentage will go backwards.
>
> Instead, we should keep the slice info when resume with an error.
>
> [email protected]
>
> (cherry picked from commit 30c71bacdda42e40654870f46d6e3278bcac113b)
>
> Bug: 837128
> Change-Id: I002c69ac4d5e1c33133e4dbddd44c3c5173a494e
> Reviewed-on: https://chromium-review.googlesource.com/1112754
> Reviewed-by: David Trainor <[email protected]>
> Reviewed-by: Min Qin <[email protected]>
> Commit-Queue: Xing Liu <[email protected]>
> Cr-Original-Commit-Position: refs/heads/master@{#571286}
> Reviewed-on: https://chromium-review.googlesource.com/1129206
> Reviewed-by: Xing Liu <[email protected]>
> Cr-Commit-Position: refs/branch-heads/3440@{#615}
> Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[email protected],[email protected],[email protected]
Change-Id: Ibafda7c82f4eaed9b6f38b3a28fa93e0404c7f6b
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 837128
Reviewed-on: https://chromium-review.googlesource.com/1129939
Reviewed-by: Xing Liu <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#620}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Reland "[vr] Tune scroll event stream"
This is a reland of 0e9a15da019624f9e5d6a3aba35b0102175da5c0
In this reland, I've combined the change with https://crrev.com/c/1124405
since the smoothing in the original CL was actually just a scaling.
Original change's description:
> [vr] Tune scroll event stream
>
> This change applies three heuristics to make trackpad scrolling feel
> smoother. We increase the frequency at which we submit scroll events to
> the platform, we also decrease the scroll scale factor (to make the
> scrolls less jumpy), and we do some simple filtering of our scroll
> values.
>
> I pair-programmed much of this change with asimjour@ and he wrote the
> initial code to interpolate events in the android ui gesture target.
>
> Bug: 859075
> Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
> Change-Id: I2fe42940214d01d99618ddacd182f202ff271dad
> Reviewed-on: https://chromium-review.googlesource.com/1120425
> Reviewed-by: Michael Thiessen <[email protected]>
> Commit-Queue: Ian Vollick <[email protected]>
> Cr-Commit-Position: refs/heads/master@{#571535}
(cherry picked from commit 98c28a6f258f58f00ef7caec2c8048b886d40df4)
Bug: 859075
Change-Id: Ib1a9f801c6930b709624233d8e00aeabc59f576d
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Reviewed-on: https://chromium-review.googlesource.com/1124908
Reviewed-by: Michael Thiessen <[email protected]>
Reviewed-by: Amirhossein Simjour <[email protected]>
Commit-Queue: Ian Vollick <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#572364}
Reviewed-on: https://chromium-review.googlesource.com/1129626
Reviewed-by: Ian Vollick <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#619}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Mac merge M68] Fix crash in safe_browsing::dmg::AnalayzeDMGFile()
This could occur if a detached code signature file is shorter than its
typical prologue.
[email protected]
(cherry picked from commit b899c92d17aeeb7d002d555558eb8fffd0177ce5)
Bug: 826761
Test: unit_tests --gtest_filter=DMGAnalyzerTest.InvalidDetachedCodeSignature
Change-Id: Ic11b12eb9ce7d7b787b7668af43e2c6ddb3abd52
Reviewed-on: https://chromium-review.googlesource.com/1114925
Commit-Queue: Robert Sesek <[email protected]>
Reviewed-by: Jialiu Lin <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#570530}
Reviewed-on: https://chromium-review.googlesource.com/1129552
Cr-Commit-Position: refs/branch-heads/3440@{#618}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Mac merge M68] Collect detached code signatures when analyzing DMG files.
A detached signature is created by codesign(1) when the signed artifact
is not Mach-O, so the resulting signature cannot be placed in the
LC_CODE_SIGNATURE command. Instead, the signature is detached into the
_CodeSignature/CodeSignature file on-disk.
This also updates the testing codesign certificate used for the
safe_browsing/mach_o test data, since new test data needed to be generated.
The existing test data were not re-signed with it, however.
[email protected]
(cherry picked from commit 0b82d4cd3484d173e7f1ec20a0de062663a20d06)
Bug: 826761
Change-Id: Ied0e96b3b0079b86679724b08aa46bf8d2669a94
Reviewed-on: https://chromium-review.googlesource.com/1101842
Reviewed-by: Ken Rockot <[email protected]>
Reviewed-by: Gayane Petrosyan <[email protected]>
Reviewed-by: Varun Khaneja <[email protected]>
Reviewed-by: Jialiu Lin <[email protected]>
Commit-Queue: Robert Sesek <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#569101}
Reviewed-on: https://chromium-review.googlesource.com/1129551
Cr-Commit-Position: refs/branch-heads/3440@{#617}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
WebView: Fix CloseGuard error in VariationsSeedLoader
The WebView requesting a variations seed opens a file descriptor to
receive the seed. We should close it after the request.
BUG=857223
Change-Id: I594067ce0c33bed2137bc39e5c133ba22bca0c04
Reviewed-on: https://chromium-review.googlesource.com/1117707
Commit-Queue: Paul Miller <[email protected]>
Reviewed-by: Richard Coles <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#571354}(cherry picked from commit 9aeb746195fa8bf7131c270af2c41c9b605bb894)
Reviewed-on: https://chromium-review.googlesource.com/1129479
Reviewed-by: Paul Miller <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#616}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Download: Fix an issue that download percentage can move backwards.
On certain Android devices, when disconnecting from WIFI, the network
code will report NETWORK_TIMEOUT before NETWORK_DISCONNECT and trigger
auto download resumption. And we erase the data downloaded by parallel
requests, so the download percentage will go backwards.
Instead, we should keep the slice info when resume with an error.
[email protected]
(cherry picked from commit 30c71bacdda42e40654870f46d6e3278bcac113b)
Bug: 837128
Change-Id: I002c69ac4d5e1c33133e4dbddd44c3c5173a494e
Reviewed-on: https://chromium-review.googlesource.com/1112754
Reviewed-by: David Trainor <[email protected]>
Reviewed-by: Min Qin <[email protected]>
Commit-Queue: Xing Liu <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#571286}
Reviewed-on: https://chromium-review.googlesource.com/1129206
Reviewed-by: Xing Liu <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#615}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[NTP Button] Moves native calls to post native initialization
> The variations check was previously happening before native
was initialized
> Moves the check to after the native library is ready
(cherry picked from commit 7b01abd45df53a2fd46ca5fe8811898b5f5d0d75)
Bug: 847129
Change-Id: Ied97f2b9038c9cff5851f20e76339a61151a9677
Reviewed-on: https://chromium-review.googlesource.com/1076377
Reviewed-by: David Trainor <[email protected]>
Commit-Queue: Daniel Park <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#562633}
Reviewed-on: https://chromium-review.googlesource.com/1128451
Reviewed-by: Theresa <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#614}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Cancel system touches when context menu is displayed
The system touches need to be cancelled whenever the context menu is
shown in order to prevent webview interaction after the context menu is
displayed.
Wait until the context menu element is available before determining if
the element supports a displyed context menu.
Bug: 853298
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I15bd7d4148f83646763504dd8370dce49e37dff3
Reviewed-on: https://chromium-review.googlesource.com/1104989
Commit-Queue: Mike Dougherty <[email protected]>
Reviewed-by: Eugene But <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568512}(cherry picked from commit 0e46d0b168129d2e7c5ab6ca21fb88524e498f21)
Reviewed-on: https://chromium-review.googlesource.com/1129280
Reviewed-by: Mike Dougherty <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#613}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[iOS] Add additional Context Menu metrics.
The ContextMenu.DelayedElementDetails metric ensures that all awaiting
requests are eventually processed by either the user cancelling or by
the DOM element details being returned.
The ContextMenu.CancelSystemTouches metric logs that the system touches
were cancelled. This value should match the number of Context Menus
shown, otherwise a user could continue to interact with the page after
the Context Menu has been displayed.
Bug: 817517, 856234
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I4dc5d9d14eba12c06ca034b80c037bd673230878
Reviewed-on: https://chromium-review.googlesource.com/1102994
Commit-Queue: Mike Dougherty <[email protected]>
Reviewed-by: Eugene But <[email protected]>
Reviewed-by: Robert Kaplow <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568450}(cherry picked from commit 9781ec3860643f79d510ead331b0d74c21c10a13)
Reviewed-on: https://chromium-review.googlesource.com/1129279
Reviewed-by: Mike Dougherty <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#612}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Typed URLs] Avoid sending history backend notifications after a DB error
Before this CL, there was a race condition in addressing DB errors in
HistoryBackend. When HistoryBackend::DatabaseErrorCallback got called,
it immediately notified TypedURLSyncBridge and posted a task to kill the
database. Before the database gets really killed, some other tasks can
run such as tasks from the expirer that result in the bridge being
notified about history deletions. The bridge does not expect backend
notifications after being notified about DB error (which makes sense).
This CL resolves this bug and delays the notification to the bridge so
that it happens synchronously with killing the DB.
The conflict in the unit-test was a trivial one (the context where the
new test is appended has changed).
[email protected]
(cherry picked from commit 40f00aa570a7a330acd74192ebacc840e9ca9d58)
Bug: 853395
Change-Id: I03d1a5c49254184e430c1619049e66895bf6dcfe
Reviewed-on: https://chromium-review.googlesource.com/1105821
Commit-Queue: Jan Krcal <[email protected]>
Reviewed-by: Mikel Astiz <[email protected]>
Reviewed-by: Scott Violet <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568554}
Reviewed-on: https://chromium-review.googlesource.com/1128096
Reviewed-by: Jan Krcal <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#611}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.56
[email protected]
Change-Id: I53622fbee5857a0ab2a82a30fbd2aa39cec0153d
Reviewed-on: https://chromium-review.googlesource.com/1128602
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#610}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.55
[email protected]
Change-Id: I3fbde36520a223a40f0ae5403ecb425dcec1ce78
Reviewed-on: https://chromium-review.googlesource.com/1128414
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#609}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[M68] [ServiceWorker] Stop observing EmbeddedWorkerInstance once it's gone away
This CL is a combination of the 2 previous commits on trunk, both of
them aim to avoid use-after-free behavior on the raw pointer of an
EmbeddedWorkerInstance.
After the 1st CL landed on trunk, it turns out that it did not fix the
problem completely and caused regressions like issue 856969, then we
have the 2nd CL give a complete solution.
The 1st one:
"
[ServiceWorker] Avoid using stale pointer of EmbeddedWorkerInstance
We're saving the raw pointer of an EmbeddedWorkerInstance in a
base::ScopedObserver member of ServiceWorkerRegisterJob, but, the
EmbeddedWorkerInstance is not guaranteed to outlive the
ServiceWorkerRegisterJob, it may get destroyed and lead to a situation
that ServiceWorkerRegisterJob holds a stale pointer, which could lead
to crash.
This CL lets ServiceWorkerRegisterJob listen OnDetached() from the
EmbeddedWorkerInstance so it can be aware that the EmbeddedWorkerInstanc
pointer is going to be stale and should be removed from the source list
of base::ScopedObserver.
This fix should be safe enough now, but in longer term we'll try to
remove EmbeddedWorkerInstance::Listener interface and let
EmbeddedWorkerInstance talk directly to its owner ServiceWorkerVersion,
then let ServiceWorkerRegisterJob observe the ServiceWorkerVersion it's
manipulating to get OnScriptLoaded() notification.
BUG=854063,855394
Change-Id: I9c5a46beda1aafff32a86b9055be2b53d50fda97
Reviewed-on: https://chromium-review.googlesource.com/1112904
Commit-Queue: Han Leon <[email protected]>
Reviewed-by: Matt Falkenhagen <[email protected]>
Cr-Commit-Position: refs/heads/master@{#569906}
(cherry picked from commit 26f26cd82a8159dff52fdef10b0a7ebb84c48040)
"
The 2nd one:
"
[ServiceWorker] Stop observing EmbeddedWorkerInstance once it's gone away
This CL adds a function OnDestroyed() into
EmbeddedWorkerInstance::Listener interface, so that
ServiceWorkerRegisterJob can stop observing EmbeddedWorkerInstance once
it's gone away.
BUG=856969,856330
Change-Id: I3acc9143f9ea2f8f24ab0aac465f29f97fdf9906
Reviewed-on: https://chromium-review.googlesource.com/1118006
Commit-Queue: Han Leon <[email protected]>
Reviewed-by: Matt Falkenhagen <[email protected]>
Cr-Commit-Position: refs/heads/master@{#571417}
(cherry picked from commit 1c81791b45c09b52614f85a7016425b71da32c4d)
"
BUG=854063,856969
Change-Id: I91c68d8edba41f6f7725903288fd12ec7574c538
Reviewed-on: https://chromium-review.googlesource.com/1128469
Reviewed-by: Matt Falkenhagen <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#608}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.54
[email protected]
Change-Id: I1886764b963cd6befdbd959b7eec4fa4ab2d939a
Reviewed-on: https://chromium-review.googlesource.com/1128405
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#607}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Stop streams associated to removed devices in MediaDevicesManager.
This fixes a bug where removing a device did not result in stopping all
its associated streams.
A unit test for this requires a minor refactoring to remove the
MediaStreamManager dependency from MediaDevicesManager, and will be
provided in a follow-up CL. This CL is deliberately simple in order to
make merging easier.
Bug: 856658
Change-Id: I84ef2856195cc7650bb08992d2095f8f853e9ea9
Reviewed-on: https://chromium-review.googlesource.com/1124323
Reviewed-by: Henrik Boström <[email protected]>
Commit-Queue: Guido Urdaneta <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#572176}(cherry picked from commit 0fe699a8dfc9c3a6cc0203759561284d634f4a57)
Reviewed-on: https://chromium-review.googlesource.com/1125959
Reviewed-by: Guido Urdaneta <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#606}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Do not delete the media ContextProvider inside the lost context callback
Currently the GpuVideoAcceleratorFactoriesImpl will check for context
loss every time it tries to use the GL context, and destroy it
immediately if it sees a loss. This is problematic if the
ContextProvider is still on the callstack, which it is if we're inside
the context loss callback. Instead, leave the ContextProvider alive
until the GpuVideoAcceleratorFactoriesImpl stops being used.
[email protected], [email protected]
(cherry picked from commit 3071401e1b0257d029a6560a9fa8c3c1f695f839)
Bug: 849131
Change-Id: I8ec66671b4bbf5d426cb5fb184653a5863de9fd9
Reviewed-on: https://chromium-review.googlesource.com/1104777
Commit-Queue: danakj <[email protected]>
Reviewed-by: Frank Liberato <[email protected]>
Reviewed-by: Antoine Labour <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568256}
Reviewed-on: https://chromium-review.googlesource.com/1128214
Reviewed-by: danakj <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#605}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Merge to M68: Bubble logical scrolling from OOPIFs.
[email protected],[email protected],[email protected]
Bubble logical scrolling from OOPIFs.
Currently, ScrollManager::BubblingScroll only bubbles logical scrolls
from an iframe when the parent is a local frame. Now, when bubbling
reaches a local root, we send an IPC to the parent's process to
continue bubbling from the frame owner element.
(cherry picked from commit e21d23b8427576ae3877a2d1616fec42dc861ed1)
Bug: 852932
Change-Id: I312aed8eea353957b7d77cea3caad60a2c3493d6
Reviewed-on: https://chromium-review.googlesource.com/1106279
Commit-Queue: Kevin McNee <[email protected]>
Reviewed-by: Daniel Cheng <[email protected]>
Reviewed-by: Charlie Reis <[email protected]>
Reviewed-by: David Bokan <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#571484}
Reviewed-on: https://chromium-review.googlesource.com/1128211
Reviewed-by: Kevin McNee <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#604}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Merge "Fix LoginUIserviceLoginPopupTest.ShowLoginPop test on Beta."
The old sign-in page requres component extensions. The unittest needs
to create the ExtensionService before loading the page.
Bug: 859438
Change-Id: I22296316346ee0f7e780babd6125cf388e920d03
Reviewed-on: https://chromium-review.googlesource.com/1125210
Reviewed-by: Mihai Sardarescu <[email protected]>
Commit-Queue: Owen Min <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#572597}(cherry picked from commit 215bd7442d675352b423caf39ff6087b62fe8459)
Reviewed-on: https://chromium-review.googlesource.com/1127936
Reviewed-by: Owen Min <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#603}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Catch java.lang.IllegalArgumentException in parsing baae64
BUG=829628
[email protected]
(cherry picked from commit 7880981a0cc24217dc87675bb12b216d02f4141d)
Change-Id: I054c8a40cf065d0c2f42bd8de9e5de6fed3fb9e9
Reviewed-on: https://chromium-review.googlesource.com/1059155
Commit-Queue: Yaron Friedman <[email protected]>
Reviewed-by: Yaron Friedman <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#561876}
Reviewed-on: https://chromium-review.googlesource.com/1127881
Reviewed-by: Tatiana Gornak <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#602}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.53
[email protected]
Change-Id: Ic05fbd55bf3e0934c7f2c7b0474c896a4856d17b
Reviewed-on: https://chromium-review.googlesource.com/1127270
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#601}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.52
[email protected]
Change-Id: I329dd454c01eb13d3d748854badf7464723a1c0f
Reviewed-on: https://chromium-review.googlesource.com/1126601
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#600}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Surface synchronization: Remove check in LayerTreeImpl
We still get the occasional surface invariants violations in the wild and
we don't necessarily want to crash the renderer in this case. We will already
log things appropriately.
Bug: 672962, 828741
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I262850f2cf704cd59366da6dd4d154227aab5220
Reviewed-on: https://chromium-review.googlesource.com/1112491
Reviewed-by: Saman Sami <[email protected]>
Commit-Queue: Fady Samuel <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#569781}(cherry picked from commit e59b611ddde7200d14b873183bc1ac48f5747a41)
Reviewed-on: https://chromium-review.googlesource.com/1126500
Reviewed-by: Fady Samuel <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#599}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
android: Retry detached requests on network change.
Some detached requests fail because the network changes between
requests. Retry the request in this case, only once.
Bug: 851399
Change-Id: Ic77c28e5ac49fecaf634e4a225c8f443f75e2560
Reviewed-on: https://chromium-review.googlesource.com/1118262
Reviewed-by: Michael van Ouwerkerk <[email protected]>
Commit-Queue: Benoit L <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#571173}(cherry picked from commit 0c88d2db535f6c407afb185e8eb40edca2b10f13)
Reviewed-on: https://chromium-review.googlesource.com/1125759
Reviewed-by: Benoit L <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#598}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Make mime handlers inherit the session storage of their embedders.
Mime handlers create a nested WebContents to contain the mime handler
extension. Currently, these run with a separate session storage
namespace, resulting in session storage being cleared if a tab recreates
a mime handler, such as due to a reload. Change mime handler WebContents
creation to inherit the session storage namespaces of their embedders so
the session storage behaves similarly to iframes within a single tab.
[email protected]
(cherry picked from commit 69a3377d60d1418a44a599b87210881d1f5fc59b)
Bug: 819761
Change-Id: I3b4f653836190ed86572eb12cdbeef3fbc157683
Reviewed-on: https://chromium-review.googlesource.com/1116633
Commit-Queue: John Abd-El-Malek <[email protected]>
Reviewed-by: John Abd-El-Malek <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#570814}
Reviewed-on: https://chromium-review.googlesource.com/1124736
Reviewed-by: Sam McNally <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#597}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.51
[email protected]
Change-Id: I6887bece3a85c681b1c34b78eeaf89c543e2f345
Reviewed-on: https://chromium-review.googlesource.com/1125441
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#596}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Merge M68] Extensions: Show file access toggle for activeTab extensions.
r548269 disallowed implicit file url access for extensions with activeTab. This
CL ensures that the file access toggle is visible for extensions using the
activeTab permission, hence providing a way for these extensions to be used on
file urls.
BUG=850643
TEST=Install an extension with activeTab permission. (E.g.
https://chrome.google.com/webstore/detail/page-redder/difbeimhegehkihppkgdlpongficimep?hl=en).
Ensure that "Allow access to file URLs" checkbox is shown for the extension.
[email protected]
Change-Id: I777c8edb29666343f2e5a6e7a1a06a32746178a8
Reviewed-on: https://chromium-review.googlesource.com/1096352
Commit-Queue: Karan Bhatia <[email protected]>
Reviewed-by: Istiaque Ahmed <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#566610}(cherry picked from commit 396ced81d62743154629327f121a407db5969e49)
Reviewed-on: https://chromium-review.googlesource.com/1124909
Reviewed-by: Karan Bhatia <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#595}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Keep reference to child ComputedStyle on stack.
Apparently, the ComputedStyle on a child may change during
LayoutBlock::ComputeBlockPreferredLogicalWidths. We used to keep a
reference to the ComputedStyle on the stack before [1]. Re-introducing
scoped_refptr here.
The reduced test exposed a DCHECK problem tracked by 389648. Instead of
adding an almost identical new test, with another TestExpections line,
we add writing-mode to the existing test which would expose the ASAN
issue as well.
[1] https://crrev.com/0aca50f1552c882bc72ed5c419085fa975847a9c
Bug: 853538, 389648
Change-Id: I5cb09c8cd9a7ae6d0621758f4690fce2abbb8096
Reviewed-on: https://chromium-review.googlesource.com/1117697
Commit-Queue: Rune Lillesveen <[email protected]>
Reviewed-by: Morten Stenshorne <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#571199}(cherry picked from commit b0a9cfb77595d3291e9d94beaa0ca3fef68bd76b)
Reviewed-on: https://chromium-review.googlesource.com/1125179
Cr-Commit-Position: refs/branch-heads/3440@{#594}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
ozone: Add low pressure filter for touchscreen
To prevent poor quality touches on hana, add a filter for low pressure
touches, such as those generated by a pencil. Finger presses are above
the chosen threshold and aren't affected. If a contact ever exceeds the
presure threshold, all remaining events for that contact are sent.
CQ-DEPEND=CL:1093584
BUG=b:69232663
TEST=manual testing on hana with pressure filter enabled
Change-Id: Ic2d56eb656e318ee46744ef37f6055d8573a2261
Reviewed-on: https://chromium-review.googlesource.com/1096126
Reviewed-by: Nico Weber <[email protected]>
Reviewed-by: Michael Spang <[email protected]>
Commit-Queue: Sean O'Brien <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#569415}(cherry picked from commit e5ba742d9cdff72d0d600440ceb03f018feee1f6)
Reviewed-on: https://chromium-review.googlesource.com/1125039
Reviewed-by: Kevin Schoedel <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#593}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Payments] Open new foreground tab triggered by user in payment handler window in browser
[email protected]
(cherry picked from commit fdadc5fd459664599074bb8557528a1b8814c65d)
Bug: 856743
Change-Id: Icee41ddd6bd4d593ae19b12ac601644d0a004be1
Reviewed-on: https://chromium-review.googlesource.com/1115803
Commit-Queue: Ganggui Tang <[email protected]>
Reviewed-by: Mathieu Perreault <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#570796}
Reviewed-on: https://chromium-review.googlesource.com/1125087
Cr-Commit-Position: refs/branch-heads/3440@{#592}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Hide incognito switch when incognito is not enabled
In cases where incognito is disabled due to a policy, we should
not see the incognito switch button at all for horizontal tab switcher.
This is in line with having the related menu item for incognito being
disabled
BUG=859160
Change-Id: I6bc19ce27fedc12fc18a9f91f5a7b433c7fb6c82
Reviewed-on: https://chromium-review.googlesource.com/1123405
Commit-Queue: Yusuf Ozuysal <[email protected]>
Reviewed-by: Matthew Jones <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#572045}(cherry picked from commit 3339971f2bff1bdfefd16fdf28d2528b61b8dfc5)
Reviewed-on: https://chromium-review.googlesource.com/1125040
Reviewed-by: Yusuf Ozuysal <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#591}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Revert "[vr] Tune scroll event stream"
This reverts commit 7b648651b1ac5f0a40a118ffb39249b09ea92724.
Reason for revert: did not address scrolling issues.
Original change's description:
> [vr] Tune scroll event stream
>
> This change applies three heuristics to make trackpad scrolling feel
> smoother. We increase the frequency at which we submit scroll events to
> the platform, we also decrease the scroll scale factor (to make the
> scrolls less jumpy), and we do some simple filtering of our scroll
> values.
>
> I pair-programmed much of this change with asimjour@ and he wrote the
> initial code to interpolate events in the android ui gesture target.
>
> (cherry picked from commit 0e9a15da019624f9e5d6a3aba35b0102175da5c0)
>
> Bug: 859075
> Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
> Change-Id: I2fe42940214d01d99618ddacd182f202ff271dad
> Reviewed-on: https://chromium-review.googlesource.com/1120425
> Reviewed-by: Michael Thiessen <[email protected]>
> Commit-Queue: Ian Vollick <[email protected]>
> Cr-Original-Commit-Position: refs/heads/master@{#571535}
> Reviewed-on: https://chromium-review.googlesource.com/1123463
> Reviewed-by: Ian Vollick <[email protected]>
> Cr-Commit-Position: refs/branch-heads/3440@{#584}
> Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[email protected]
Change-Id: I5ba9707aea9dbde21910358df0e599a21085f715
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 859075
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Reviewed-on: https://chromium-review.googlesource.com/1124821
Reviewed-by: Ian Vollick <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#590}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Updating XTBs based on .GRDs from branch 3440
[email protected]
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I6de2a304bb0c543c008d58a0a6ee22bdafb12759
Reviewed-on: https://chromium-review.googlesource.com/1124673
Reviewed-by: Krishna Govind <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#589}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[AF][IOS] Aligns the credit card save infobar icon with the title label
- Replaces the credit card save infobar icon with a new one with smaller
intrinsic padding so it can be better aligned with the title text.
- Also adjusts the line height of the labels in the infobar.
- New PNGs are pngcrushed.
TBR=mathp
Bug: 854246
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I0425e43e3d44b058df3badd7dd1fa8d16d5787e6
Reviewed-on: https://chromium-review.googlesource.com/1111013
Commit-Queue: Moe Ahmadi <[email protected]>
Reviewed-by: Kurt Horimoto <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#569508}(cherry picked from commit 7ccd5d7cb077235d6e9a7eefcc92b3841267a0e3)
Reviewed-on: https://chromium-review.googlesource.com/1124819
Reviewed-by: Moe Ahmadi (slow July 3) <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#588}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
VR: remove fullscreen toast on standalones
Bug: 854181
Change-Id: Id2418b88928fcd998e67bed8f011f2dcbb4cc8f5
Reviewed-on: https://chromium-review.googlesource.com/1106293
Reviewed-by: Ted Choc <[email protected]>
Reviewed-by: Michael Thiessen <[email protected]>
Commit-Queue: Amirhossein Simjour <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#569036}(cherry picked from commit d2e9c37af31979c907e2a497eb72e1d89b0f34ab)
Reviewed-on: https://chromium-review.googlesource.com/1124700
Reviewed-by: Amirhossein Simjour <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#587}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
ozone: Allow multiple delay filters for touchscreen
In order to allow more than one touch filter to delay the reporting of
touches, make the existing filter keep track of its own filter state.
BUG=b:69232663
TEST=manual testing with filters enabled
Change-Id: Idfc68fea22574becd920cdd599dd2e90e19bd04d
Reviewed-on: https://chromium-review.googlesource.com/1093584
Reviewed-by: Michael Spang <[email protected]>
Commit-Queue: Sean O'Brien <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#567844}(cherry picked from commit b42a277d0612b3d982941cb144d4b7b00bbf96f4)
Reviewed-on: https://chromium-review.googlesource.com/1120756
Reviewed-by: Kevin Schoedel <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#586}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Fix InitializeOnAudioThread race.
It may race with ShutdownOnAudioThread when running the audio service
out of process.
Bug: 854816
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: I2ccd4254f4c4f0f70ffb2180c3a586e35ce1baed
Reviewed-on: https://chromium-review.googlesource.com/1109683
Reviewed-by: Henrik Grunell <[email protected]>
Commit-Queue: Max Morin <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#570029}(cherry picked from commit 75c63f8b8f1f19874867ac05a60c4ebe89496e1a)
Reviewed-on: https://chromium-review.googlesource.com/1124479
Reviewed-by: Olga Sharonova <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#585}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[vr] Tune scroll event stream
This change applies three heuristics to make trackpad scrolling feel
smoother. We increase the frequency at which we submit scroll events to
the platform, we also decrease the scroll scale factor (to make the
scrolls less jumpy), and we do some simple filtering of our scroll
values.
I pair-programmed much of this change with asimjour@ and he wrote the
initial code to interpolate events in the android ui gesture target.
(cherry picked from commit 0e9a15da019624f9e5d6a3aba35b0102175da5c0)
Bug: 859075
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I2fe42940214d01d99618ddacd182f202ff271dad
Reviewed-on: https://chromium-review.googlesource.com/1120425
Reviewed-by: Michael Thiessen <[email protected]>
Commit-Queue: Ian Vollick <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#571535}
Reviewed-on: https://chromium-review.googlesource.com/1123463
Reviewed-by: Ian Vollick <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#584}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.50
[email protected]
Change-Id: Ia0878fb0ce8dcb7ee93004313effc94a5ca1c3ec
Reviewed-on: https://chromium-review.googlesource.com/1123622
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#583}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Avoid unnecessary SharedBuffer data segmentation
When constructing SharedBuffers from flat data, we currently defer to
SharedBuffer::AppendInternal() -- which splits the source into segments.
This is unnecessary overhead (because SharedBuffer can already track a
single flat slab in buffer_), and can generate even more churn
downstream for clients which require a flattened data view (we're
effectively splitting then reassembling the data source for no reason).
Update SharedBuffer's flat data constructors to store all the data
contiguously in buffer_ (similar to SharedBuffer::AdoptVector).
Bug: 853500
Change-Id: I523f23859e62c76225c8d5345005c5bd7911d9c3
Reviewed-on: https://chromium-review.googlesource.com/1113661
Reviewed-by: Kentaro Hara <[email protected]>
Reviewed-by: Hajime Hoshi <[email protected]>
Commit-Queue: Florin Malita <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#570385}(cherry picked from commit ce42a9d24c7aac91d073851e2ed4fc3180a8384d)
Reviewed-on: https://chromium-review.googlesource.com/1123037
Reviewed-by: Florin Malita <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#582}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Fix a crash on early releases of macOS 10.10.
So far, all instances of this missing selector crash linked in the bug have
come from 10.10.0, but my copy of 10.10 has it. This change checks
`respondsToSelector:`, instead of OS version, before calling SPI.
Bug: 856211
Change-Id: Ib2aa07e0e24b83f1766a2f6e16e19b2b123970a6
Reviewed-on: https://chromium-review.googlesource.com/1115781
Reviewed-by: Avi Drissman <[email protected]>
Commit-Queue: Sidney San Martín <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#571123}(cherry picked from commit f44f7dc221536b3d72c76322f17dc04fc04d892d)
Reviewed-on: https://chromium-review.googlesource.com/1123176
Reviewed-by: Sidney San Martín <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#581}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Media Controls: Fix sizing issues with medium and large breakpoints
This CL updates the sizing-medium and sizing-large CSS class rules to
reduce the sizes. This update makes sizing-large mostly useless, but to
avoid making this change too complex for merging into M68, we are
updating the CSS rules in the simplest way and have added a followup
cleanup task to remove the sizing-large CSS class and other redundant
CSS rules.
Bug: 857145
Change-Id: Ifd80ff7137221f4ca86d0c27f7c4042ec569ef06
Reviewed-on: https://chromium-review.googlesource.com/1117315
Commit-Queue: Tommy Steimel <[email protected]>
Reviewed-by: Becca Hughes <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#571190}(cherry picked from commit b5073e2a388dd2ab9445c8101ab0ca265eaa79fc)
Reviewed-on: https://chromium-review.googlesource.com/1123116
Reviewed-by: Tommy Steimel <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#580}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Updating XTBs based on .GRDs from branch 3440
[email protected]
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.linux:closure_compilation;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I1a50f0752ba631fdfa36280b6a8645d715a59491
Reviewed-on: https://chromium-review.googlesource.com/1122975
Reviewed-by: Krishna Govind <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#579}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.49
[email protected]
Change-Id: I9d097f4955b9ba09c28e3e3c60abf4315146c6f9
Reviewed-on: https://chromium-review.googlesource.com/1121896
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#578}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.48
[email protected]
Change-Id: I2de2957426223c01b8c09fb4d46e713ef8640e40
Reviewed-on: https://chromium-review.googlesource.com/1121528
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#577}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Merge M68][Extensions] Update captureVisibleTab permission checks
tabs.captureVisibleTab() is interesting. It used to work with every
URL ever, and just checked for if activeTab or <all_urls> was present.
However, this led to some issues where the extension could capture pages
it shouldn't be able to, such as https://crbug.com/810220.
Changing this to only allow access to pages that the extension had
explicit access to also broke important use cases. For instance, taking
screenshots of chrome:-scheme pages is important for filing bugs,
tracking features, etc. This similarly broke use cases for other URLs
that extensions don't have full access to, like other extensions' pages.
An exception was added for chrome:-scheme pages, but this was
insufficient for other cases.
Adjust the permissions check to allow page capture of otherwise-
restricted pages if the extension has activeTab granted. We require
activeTab (rather than either <all_urls> or activeTab) because it gives
a stronger guarantee that the user wants the extension to run on the
given site.
Note: this does not allow any other action on these restricted pages;
only capturing the page is permitted.
The new behavior enforces the following permission requirements for
the host types:
<arbitrary web page>: activeTab OR <all_urls>
file:-scheme page: (activeTab OR <all_urls>) AND
explicit file access from chrome://extensions.
Pages restricted by enterprise policy: blocked
Extension's own page: activeTab OR <all_urls>
Another extension's page: activeTab
chrome:-scheme page: activeTab
Support for IPv6 pages and pseudo urls is dependent on these being
properly supported with activeTab, which will be pursued in a followup.
Bug: 839857
[email protected]
(cherry picked from commit 955451dfb49b6cf59dc805737773e944701f9202)
Change-Id: Ied3a71732cd5d41ad16f9b459f6fda9b1815edaf
Reviewed-on: https://chromium-review.googlesource.com/1102902
Reviewed-by: Karan Bhatia <[email protected]>
Commit-Queue: Devlin <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568471}
Reviewed-on: https://chromium-review.googlesource.com/1121380
Reviewed-by: Devlin <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#576}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.47
[email protected]
Change-Id: Id1269ec2bc6d109d400c9507e061a6c13bd0650c
Reviewed-on: https://chromium-review.googlesource.com/1121518
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#575}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Media Controls] Update sizing CSS to new specs
This CL makes some changes to the media controls sizing. It changes the
small threshold to go up to 740px instead of 640px, it changes the
overlay play button size calculation to be smaller, and it changes the
icons to be smaller in the medium threshold.
Bug: 854361
Change-Id: Ic73d254361ffbb5b60bb974253d1abb48a8a04ce
Reviewed-on: https://chromium-review.googlesource.com/1107244
Commit-Queue: Tommy Steimel <[email protected]>
Reviewed-by: Becca Hughes <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#569044}(cherry picked from commit 8b04a2116d5522871b7110eb0a9d75d044e6cee0)
Reviewed-on: https://chromium-review.googlesource.com/1119372
Reviewed-by: Tommy Steimel <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#574}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Discard tab immediately without waiting for LogMemory().
LogMemory() calls memory::OomMemoryDetails::Log(), which is an async
call and may take a long time (only 60% returns < 1s, 10% returns > 5s).
When we're running out of memory, we need to discard tab faster.
BUG=850545
Change-Id: Ia652b2a80f968b0e437904bb6bc2c7c131c1958d
Reviewed-on: https://chromium-review.googlesource.com/1097038
Reviewed-by: Cheng-Yu Lee <[email protected]>
Reviewed-by: Trent Apted <[email protected]>
Reviewed-by: Erik Chen <[email protected]>
Reviewed-by: François Doray <[email protected]>
Commit-Queue: Cheng-Yu Lee <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#567891}(cherry picked from commit 9f5206473f137a0ea67c645b5d9798059393c08f)
Reviewed-on: https://chromium-review.googlesource.com/1121176
Cr-Commit-Position: refs/branch-heads/3440@{#573}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Media Controls] Prevent the overlay enclosure from being 0x0
This CL adds CSS to make the overlay enclosure the size of the video
to prevent it from defaulting to 0x0. This fixes a bug where once the
overlay cast button disappeared (due to the hide timer), the user was
unable to bring it back by tapping on the overlay enclosure (since
there was nothing to tap on).
Bug: 853855
Change-Id: If4504b84c023cf7f52620ce7d58a71a5522be587
Reviewed-on: https://chromium-review.googlesource.com/1105516
Commit-Queue: Tommy Steimel <[email protected]>
Reviewed-by: Becca Hughes <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568644}(cherry picked from commit 47ae9e57670b0bbf3501bb8de627ea3d660cc713)
Reviewed-on: https://chromium-review.googlesource.com/1121156
Reviewed-by: Tommy Steimel <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#572}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Fix passing host name property through shill Manager interface.
https://android-review.googlesource.com/c/platform/system/connectivity/shill/+/181040
replaced the "HostName" property in the shill Manager interface with a new
"DHCPProperty.Hostname" property. However, the migration was partially done,
which has been fixed by CL:1102152. This CL updates the code on the Chrome side
accordingly.
(back ported from commit bfad34f4f4251c94ae82b8b602d293968c9927f9)
Bug: 852035
Change-Id: Ib0d7fc7e82f13b9f77cda13324702f610d952f61
Reviewed-on: https://chromium-review.googlesource.com/1104312
Reviewed-by: Steven Bennetts <[email protected]>
Commit-Queue: Ben Chan <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568092}
Reviewed-on: https://chromium-review.googlesource.com/1121038
Cr-Commit-Position: refs/branch-heads/3440@{#571}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
users_private: Do not use profile for other users
GetProfileByUser() will return null for a non logged in user, so do not
use IsOwnerProfile() to set is_owner.
This also fixes behavior in ChromeUserManagerImpl where the active user
was not correctly set as the owner when kStubCrosSettings is set
because UserManagerBase::UserLoggedIn is calling
RegularUserLoggedInAsEphemeral() instead of RegularUserLoggedIn() for
non owners, and the logic to set the user as the owner was in
RegularUserLoggedIn().
[email protected]
(cherry picked from commit ef47cfb48bba0688ced57d91b1059f03dc82b99a)
Bug: 856441
Change-Id: I085d46accb3c97c1b6ee5615b838a5de796e3f8b
Reviewed-on: https://chromium-review.googlesource.com/1118921
Commit-Queue: Steven Bennetts <[email protected]>
Reviewed-by: Alexander Alekseev <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#571341}
Reviewed-on: https://chromium-review.googlesource.com/1120947
Reviewed-by: Steven Bennetts <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#570}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Merge "Don't show popup sign in window for locked profile or guest/system profile" into 68.
Bug: 855378
Change-Id: I4c14ad013f891f6abe76604321c52e97cecaf874
Reviewed-on: https://chromium-review.googlesource.com/1115433
Reviewed-by: Mihai Sardarescu <[email protected]>
Commit-Queue: Owen Min <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#570793}(cherry picked from commit 0e92e3bf71e2feaf49a7b87b98488ca80c535d35)
Reviewed-on: https://chromium-review.googlesource.com/1120465
Reviewed-by: Owen Min <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#569}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[signin] Reconcilor handles invalidated cookies
Invalidated cookies were not handled correctly. This CL adds proper
support for them.
[email protected], treib
(cherry picked from commit 4d83639996b796350efcedbfd861cc9c520af524)
Bug: 854799
Change-Id: Iad3ee729172a7e44d737b25fb665f0009d78de84
Reviewed-on: https://chromium-review.googlesource.com/1110218
Commit-Queue: David Roger <[email protected]>
Reviewed-by: Marc Treib <[email protected]>
Reviewed-by: Mihai Sardarescu <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#570825}
Reviewed-on: https://chromium-review.googlesource.com/1120170
Reviewed-by: David Roger <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#568}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[signin] AccountReconcilor use different Gaia sources for Dice/Mirror
The Gaia server needs to be able to distinguish between Dice and Mirror
calls.
This CL sets a new different source for Dice calls.
[email protected]
(cherry picked from commit f3c2edb0419a7f53628f98d3f82e9fdfdbd73087)
Bug: 854743
Change-Id: Id697d5aad326283b0002c6ce76dde4e619b9885e
Reviewed-on: https://chromium-review.googlesource.com/1109898
Reviewed-by: Mihai Sardarescu <[email protected]>
Commit-Queue: David Roger <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#569681}
Reviewed-on: https://chromium-review.googlesource.com/1120167
Reviewed-by: David Roger <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#567}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.46
[email protected]
Change-Id: I4152845d8b0a2d733c7878f1196e6575af1ccc88
Reviewed-on: https://chromium-review.googlesource.com/1119409
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#566}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Updating XTBs based on .GRDs from branch 3440
[email protected]
Change-Id: I73205dd3b8e94815861c7b72f73772a422cc0cc7
Reviewed-on: https://chromium-review.googlesource.com/1119381
Reviewed-by: Krishna Govind <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#565}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Change our ellipsize in FramebustBlockInfoBar.
When using a layout with ellipsize=start on old versions of Android a
crash can result. This is a speculative fix that changes the way we
ellipsize to "middle" to workaround this crash.
BUG=834959
Change-Id: I0330d9eee82400983e4407bb8a558e322cbf4482
Reviewed-on: https://chromium-review.googlesource.com/1107169
Commit-Queue: Donn Denman <[email protected]>
Reviewed-by: Matthew Jones <[email protected]>
Reviewed-by: Theresa <[email protected]>
Reviewed-by: Anita Woodruff <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#570121}(cherry picked from commit 1242f8a4d3058caf32df6545a86cf9bf25aa0699)
Reviewed-on: https://chromium-review.googlesource.com/1119266
Reviewed-by: Donn Denman <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#564}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[PE] Don't fragment painting layer of repeating table header/footer in paged media
Previously, to let the painting layer of a repeating table header/footer
in paged media initiate multi-fragment painting, we created fragments
in the painting layer. This caused several problems:
- The fragments didn't have proper fragment clips, causing non-fragmented
contents to be painted multiple times. It's also not feasible to create
fragment clips for the forced fragments on the painting layer because
we couldn't insert them into the clip tree.
- The previous "if (paint_info.FragmentToPaint(layout_table_section_))
return;" in TableSectionPainter caused nested repeating header/footer
not repeated.
Now don't fragment painting layer of repeating table header/footer in
paged media. Instead, let the repeating table header/footer repeat by
itself when needed.
[email protected]
(cherry picked from commit cf69822f0cdf24a24cce2f92fdfe029ba2cf7dfb)
Bug: 852773
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I1172a334b5021eb7e987404bb72d9b841a4d39d4
Reviewed-on: https://chromium-review.googlesource.com/1112578
Commit-Queue: Xianzhu Wang <[email protected]>
Reviewed-by: Chris Harrelson <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#569901}
Reviewed-on: https://chromium-review.googlesource.com/1119083
Reviewed-by: Xianzhu Wang <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#563}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Fix CTS webkit.WebViewHostSideStartupTest#testStrictMode
This patch only fix one violation caused by
WebViewChromiumFactoryProvider.initialize()
[email protected]
(cherry picked from commit 47262f5240d73f57606389365f499d334a931c0d)
Bug: 857121
Change-Id: Ida7d2b3df4e0e7c96f69e42e0b766dde976b2c3a
Reviewed-on: https://chromium-review.googlesource.com/1117268
Commit-Queue: Tao Bai <[email protected]>
Reviewed-by: Changwan Ryu <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#570931}
Reviewed-on: https://chromium-review.googlesource.com/1117841
Reviewed-by: Tao Bai <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#562}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.45
[email protected]
Change-Id: I2ca230368c67d5ce5f754162a7ae7613eecb092c
Reviewed-on: https://chromium-review.googlesource.com/1117616
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#561}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
chrome.bluetoothSocket: Fix regression in send()
In https://crrev.com/c/997098, params_ was changed to a local variable,
but it needs to last longer than that since net::WrappedIOBuffer may use
the data after the local variable goes out of scope.
This CL changed it back to be an instance variable.
[email protected]
(cherry picked from commit c5c6320f80159dc41dffc3cfbf0298925c7dcf1b)
Bug: 851799
Change-Id: I392f8acaef4c6473d6ea4fbee7209445aa09112e
Reviewed-on: https://chromium-review.googlesource.com/1103676
Reviewed-by: Toni Barzic <[email protected]>
Commit-Queue: Sonny Sasaka <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568137}
Reviewed-on: https://chromium-review.googlesource.com/1117649
Reviewed-by: Miao-chen Chou <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#560}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Updating XTBs based on .GRDs from branch 3440
[email protected]
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.linux:closure_compilation;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I9ef1c4feface6438102c3889958159535d192dac
Reviewed-on: https://chromium-review.googlesource.com/1117470
Reviewed-by: Krishna Govind <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#559}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
SecondaryUiMd on by default for CrOS
Enables Harmony dialog styling by default on Chrome OS dialogs. Also
see launch bug crbug.com/839559.
Bug: 783540
Test: Summon any dialog (blockers of 783540) that has been Harmonized.
Verify that it has the Harmonious styling.
Change-Id: I2c9340d33d0d404edec2b110fe4dd9d6727bc645
Reviewed-on: https://chromium-review.googlesource.com/1072727
Reviewed-by: Scott Violet <[email protected]>
Reviewed-by: Elly Fong-Jones <[email protected]>
Commit-Queue: Greg Levin <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568576}(cherry picked from commit db0e213a037aabba4e00d21c8e180af33e7a74ca)
Reviewed-on: https://chromium-review.googlesource.com/1117519
Reviewed-by: Greg Levin <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#558}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Fix AXTreeSourceAuraTest.Accessors when Harmony is on.
When Harmony is enabled textfields have an additional child in the form
of the focus ring, so the expectation needed to be updated.
Merging to M-68 because this fixes a test which is broken by
https://chromium-review.googlesource.com/1072727
Bug: 846410
Change-Id: I0b807d7f69c97eed7bc56e9520f51d3a845fba76
Reviewed-on: https://chromium-review.googlesource.com/1103586
Reviewed-by: David Tseng <[email protected]>
Commit-Queue: Bret Sepulveda <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568166}(cherry picked from commit d5010c9c9cff2a30d9d495d9c7a953da308ffa45)
Reviewed-on: https://chromium-review.googlesource.com/1117499
Reviewed-by: Greg Levin <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#557}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Fix SadTabViewInteractiveUITest suite for Chrome OS when Refresh is on.
The test assumed BlueButton would always be used for dialog buttons,
but LabelButton is used in Harmony (which Refresh implies).
Merging to M-68 because this fixes a test which is broken by
https://chromium-review.googlesource.com/1072727
Bug: 846410
Change-Id: Id7fb8f66cc0abb120fdb81294c4d00c3faf060ae
Reviewed-on: https://chromium-review.googlesource.com/1105457
Reviewed-by: Peter Boström <[email protected]>
Commit-Queue: Bret Sepulveda <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568272}(cherry picked from commit 3183d7ced9505e878652100378d62d20a8228d47)
Reviewed-on: https://chromium-review.googlesource.com/1117518
Reviewed-by: Greg Levin <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#556}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
settings: Internet: Fix configure button spacing and vis
This CL:
* Hides the 'configure' button for non secure WiFi networks (there is
nothing to configure).
* Fixes the spacing for the 'connect' and 'disconnect' buttons.
[email protected]
(cherry picked from commit 17573c429dad1deee0c668f3933efc21e6b61a3a)
Bug: 826242,838868
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Id447a929234b90bfa4064a5daa88e5df6e95a4a4
Reviewed-on: https://chromium-review.googlesource.com/1089469
Commit-Queue: Steven Bennetts <[email protected]>
Reviewed-by: Toni Barzic <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#566131}
Reviewed-on: https://chromium-review.googlesource.com/1117464
Reviewed-by: Steven Bennetts <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#555}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Mark ProxyChangeListener as @UsedByReflection.
A number of WebView applications in the wild use reflection to call the
proxy change broadcast receiver directly as a hack to allow them to set
an application-local proxy setting. The reflection code used searches
for ProxyChangeListener by name, so fails with proguard obfuscation
enabled for the monochrome APK. Mark the relevant classes/methods as
@UsedByReflection to ensure they don't get renamed, because while it's
not good that applications do this, there is no supported API to achieve
the same thing either, and it appears to be a commonly repeated piece of
code.
[email protected]
(cherry picked from commit 0f71a543910198ee5b4104ea0066494a3fcba309)
Bug: 851995
Change-Id: I6174181491f57fd71fece91c98ae8b96f36b425f
Reviewed-on: https://chromium-review.googlesource.com/1112564
Reviewed-by: Paul Jensen <[email protected]>
Commit-Queue: Richard Coles <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#570479}
Reviewed-on: https://chromium-review.googlesource.com/1117331
Reviewed-by: Richard Coles <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#554}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.44
[email protected]
Change-Id: I70b29584237cb55917bcf053d35bd2cbf135c8ac
Reviewed-on: https://chromium-review.googlesource.com/1117033
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#553}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Use shared bold fontlist delta to avoid re-deriving it.
[email protected]
(cherry picked from commit 46300153b2ec876a63795f76c2d5040fbcfaf6c0)
Bug: 843368
Change-Id: I300f2793ee70f93275be20aa77d24296d7da05d1
Reviewed-on: https://chromium-review.googlesource.com/1087317
Reviewed-by: Dave Schuyler <[email protected]>
Reviewed-by: Justin Donnelly <[email protected]>
Commit-Queue: Travis Skare <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#565133}
Reviewed-on: https://chromium-review.googlesource.com/1117122
Cr-Commit-Position: refs/branch-heads/3440@{#552}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.43
[email protected]
Change-Id: Idfd15493de1646572c9d359bff11f8437d20d065
Reviewed-on: https://chromium-review.googlesource.com/1116979
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#551}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Disable state-preserving TPM firmware update.
The test team found an issue where cryptohomed fails to deal with the
state the TPM is in for the case when the update installation gets
interrupted and recovery is invoked to retry and complete the update.
Disable device-state preserving updates for now until the issue is
resolved.
BUG=chromium:854576
TEST=Triggering TPM firmware update via chrome://chrome will not invoke the device state preserving update flow.
Change-Id: I4ac4d325bfbf953cfa14a501e871a3f9f59c699c
Reviewed-on: https://chromium-review.googlesource.com/1111998
Reviewed-by: Steven Bennetts <[email protected]>
Commit-Queue: Mattias Nissler <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#570020}(cherry picked from commit bcbd174038035d8c59e45a067b8bea0c16168b40)
Reviewed-on: https://chromium-review.googlesource.com/1116998
Reviewed-by: Mattias Nissler <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#550}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Revert "M68 Reland "Remove blink::CallExtraOrCrash" (includes fixed)"
This reverts commit e6880fe75a2995b99bce58a418113685b5f76fe9.
Reason for revert: Breaks continuous release bots, blocking beta release.
Original change's description:
> M68 Reland "Remove blink::CallExtraOrCrash" (includes fixed)
>
> This is functionally the same as the original cherry-pick
> 17254140a1f41e6057fcb22885c6178fa82affad but with compile fixes.
>
> Also removed
> virtual/outofblink-cors/http/tests/fetch/chromium/call-extra-crash-tee.html
> and
> virtual/outofblink-cors/http/tests/fetch/chromium/release-handle-crash.html
> from SlowTests as these tests are not run in M68.
>
> Original description:
>
> CallExtraOrCrash is a function to call into V8 Extras and crash if it
> fails. Unfortunately, calling into V8 Extras can fail under normal
> conditions such as stack overflow and Worker destruction, causing a lot
> of unnecessary crashes. Remove CallExtraOrCrash.
>
> This is a stopgap change designed to be mergable to version 68. It
> avoids major code restructuring but as a result lacks robust
> encapsulation.
>
> The general strategy is to pass a boolean pointer to functions in
> ReadableStreamOperations that call into V8 Extras. If the internal call
> fails, the boolean is set to true, and the call returns a default value.
>
> BodyStreamBuffer keeps the boolean as member variable. Once a call to a
> V8 extra function fails, the boolean is set and no more calls will be
> made. This is to avoid us taking action based on information that is
> incorrect.
>
> For Tee() and the from-stream version of the BodyStreamBuffer
> constructor, we use an ExceptionState object instead. In these cases, it
> is straightforward to pass through ExceptionState object from the Blink
> bindings. This allows the failure to be propagated safely back to
> Javascript.
>
> Conversely, DefaultReaderRead() has been switched from using
> ExceptionState to using an error-signalling bool. This is because its
> callers do not have access to a real ExceptionState object. Previously
> callers used a NonThrowableExceptionState, but this was not suitable as
> DefaultReaderRead() can throw.
>
> BodyStreamBuffer mostly wraps access to ReadableStreamOperations, so
> some degree of encapsulation has been retained.
>
> 7 new layout tests exercise each of the deterministically reachable
> crashes, using stack overflows. Because they depend on stack layout and
> whether DCHECKs are enabled, they only hit the crashes in particular
> environments.
>
> [email protected], [email protected], [email protected]
>
> (cherry picked from commit 035ce793d12dbd436c609823f7160364110c9775)
>
> Bug: 829790, 849312, 853977
> Change-Id: I730a6c42da773afd9653bb2985916ffe92bb81c6
> Reviewed-on: https://chromium-review.googlesource.com/1114404
> Reviewed-by: Adam Rice <[email protected]>
> Cr-Commit-Position: refs/branch-heads/3440@{#522}
> Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[email protected],[email protected],[email protected]
# Not skipping CQ checks because original CL landed > 1 day ago.
Bug: 829790, 849312, 853977, 856902
Change-Id: Ib1207919c376d7e1fe2c392d506dfc56085dc461
Reviewed-on: https://chromium-review.googlesource.com/1116838
Reviewed-by: Juan Antonio Navarro Pérez <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#549}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[M68] Change device_id member to be by value in InputIPC.
Bug: 854589
Change-Id: Ic3df198b77eb5dca4ebd85c637d47c162a5e58bd
Reviewed-on: https://chromium-review.googlesource.com/1107807
Reviewed-by: Olga Sharonova <[email protected]>
Commit-Queue: Max Morin <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568884}(cherry picked from commit 59ea0fee3d75487dbac0581cea0991a1ad0d77df)
Reviewed-on: https://chromium-review.googlesource.com/1116579
Reviewed-by: Max Morin <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#548}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Rename the ExperimentalHardwareEchoCancellation origin trial
Renaming it to ExperimentalHardwareEchoCancellation2, so that new
tokens don't trigger the old behaviour in older versions of Chrome.
The runtime flag retains its name, since that's user controlled.
Bug: 854577, 846270
Change-Id: I577e37082ed4cd84d4e77dc6f13155a4eba49131
Reviewed-on: https://chromium-review.googlesource.com/1106338
Reviewed-by: Jochen Eisinger <[email protected]>
Commit-Queue: Oskar Sundbom <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568821}(cherry picked from commit 65a07689aec111f6af8a2de242765647f95a0f09)
Reviewed-on: https://chromium-review.googlesource.com/1116578
Reviewed-by: Henrik Grunell <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#547}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
M68: service worker: Check for shutdown in ServiceWorkerContentSettingsProxyImpl.
context_ is a weak ptr and if shutdown is happening resource_context()
is null.
Bug: 851829
Change-Id: Ie1353b4fd583f88cc791227e2afd9ba27c3d39eb
Reviewed-on: https://chromium-review.googlesource.com/1111766
Reviewed-by: Makoto Shimazu <[email protected]>
Commit-Queue: Matt Falkenhagen <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#569847}(cherry picked from commit 682d85240a60b8f846802e0eee600cef48159f3b)
Reviewed-on: https://chromium-review.googlesource.com/1116298
Reviewed-by: Matt Falkenhagen <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#546}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Merge to M68]Enable arrow key in PowerButtonController instead of PowerButtonMenuScreenView.
[email protected]
The contents view of |menu_widget_| in PowerButtonController will be updated
when showing menu, which means the destructor of PowerButtonMenuScreenView
will not be called when DismissMenu. This will cause the arrow key traversal
enabled value in FocusManager will not be restored correctly. Move the logic from
PowerbuttonMenuScreenView into PowerButtonController to make sure the value
can be restored correctly if dismiss the menu.
(cherry picked from commit a71ca1b7e6979ad89f6ae64c290422797df11b54)
Bug: 846639
Change-Id: I32ceebb8e81cf19e3fed119af0ccee3bd8c55638
Reviewed-on: https://chromium-review.googlesource.com/1114309
Commit-Queue: Min Chen <[email protected]>
Reviewed-by: Qiang Xu <[email protected]>
Reviewed-by: Dan Erat <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#570323}
Reviewed-on: https://chromium-review.googlesource.com/1116193
Reviewed-by: Min Chen <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#545}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.42
[email protected]
Change-Id: I32d2c7b94296d612d8768060364f66e1b85b8c98
Reviewed-on: https://chromium-review.googlesource.com/1116100
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#544}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Merge to M68] Omnibox UI Refresh: Always show the focus ring when focused
This merge comprises of the following two CLs together, since the
intermediate state is broken:
Omnibox UI Refresh: Always show the focus ring when focused
Previously, we only showed the focus ring on certain platforms (Mac) or
keyboard accessibility mode.
Now, following the new Material Refresh guidelines, we display the focus
ring on the Omnibox whenever it is focused (and the popup is hidden).
This also simplifies the code a bit, as keyboard accessibility mode is
no longer relevant.
Bug: 844263, 823535
Change-Id: Ic5133463f6e67af5ef6f0512034938e4a19a9972
Reviewed-on: https://chromium-review.googlesource.com/1069690
Reviewed-by: Scott Violet <[email protected]>
Commit-Queue: Tommy Li <[email protected]>
Cr-Commit-Position: refs/heads/master@{#562979}
(cherry picked from commit be652b796af75662f2d0dc64e152d8c90b14f271)
Omnibox UI Refresh: Fix legacy focus ring for keyboard accessibility
Previously we displayed a legacy focus ring if Material Refresh was off
for full keyboard accessibilty mode on all platforms.
The CL below accidentally removed it:
https://chromium-review.googlesource.com/c/chromium/src/+/1069690
Now we are adding it back with a partial revert - and a refactor to
make the logic overall more clear. We can remove everything we are
adding in this CL once Material Refresh is permanent and launched.
(cherry picked from commit 479e0af586ef7a0b0770312a9f03a13aa72910c2)
Bug: 848641, 844263, 823535
Change-Id: Ife78cd9660e38f16525b55044ee0a231101534a6
Reviewed-on: https://chromium-review.googlesource.com/1082794
Reviewed-by: Scott Violet <[email protected]>
Commit-Queue: Tommy Li <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#563814}
Reviewed-on: https://chromium-review.googlesource.com/1115432
Reviewed-by: Tommy Li <[email protected]>
Reviewed-by: Justin Donnelly <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#543}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Add UseCounters for Symantec certs to be distrusted in M70
[Merge to M68 Beta]
The old Symantec PKI will be fully distrusted in M70
(https://security.googleblog.com/2018/03/distrust-of-symantec-pki-immediate.html). We
already have DevTools console messages in place for affected resources, and this
CL adds UseCounters so that we know how many page loads will be affected.
The counters give us:
- % of page visits with an affected main frame main resource
- % of page visits with an afected subframe main resource
- % of page visits with an affected subresource
Note that these buckets can overlap, for example a single page visit can
increment all 3 counters.
[email protected]
(cherry picked from commit aaea8461122ae3c1725ba2c1a4875bd5d65787be)
Bug: 853868
Change-Id: I7ae103efcc47a3e4e381b35c6803ef2d8ed4c7fb
Reviewed-on: https://chromium-review.googlesource.com/1107841
Commit-Queue: Emily Stark <[email protected]>
Reviewed-by: Mike West <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#569282}
Reviewed-on: https://chromium-review.googlesource.com/1115898
Reviewed-by: Christopher Thompson <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#542}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Language] Add target language to chrome://settings/languages
Bug: 818242
Change-Id: Ie5295fb0c2c1605cf15a340c965a56629c6c867c
Reviewed-on: https://chromium-review.googlesource.com/1093022
Commit-Queue: anthonyvd <[email protected]>
Reviewed-by: Michael Martis <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568458}(cherry picked from commit b6f6823c013271dc49307a0b1056cc6c639517e3)
Reviewed-on: https://chromium-review.googlesource.com/1115838
Reviewed-by: anthonyvd <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#541}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[M68 merge]EventTiming: Add UseCounter to track explicit usage
This CL adds a UseCounter that tracks the two ways to use EventTiming
explicitly:
* getEntriesByType or getEntriesByName with event/firstInput.
* Having PerformanceObservers of event/firstInput.
(cherry picked from commit 4679d0a38913ec026695393dbb4ca09c68731df1)
Bug: 851484
Change-Id: I8c2af71d089dbbf7db87b94b8b5d9f56e1699998
Reviewed-on: https://chromium-review.googlesource.com/1115511
Reviewed-by: Timothy Dresser <[email protected]>
Reviewed-by: Steve Kobes <[email protected]>
Commit-Queue: Nicolás Peña Moreno <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#570539}
Reviewed-on: https://chromium-review.googlesource.com/1115732
Reviewed-by: Nicolás Peña Moreno <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#540}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Incrementing VERSION to 68.0.3440.41
[email protected]
Change-Id: I56d4388bb6ded71bb0988798e66cfaf44384db07
Reviewed-on: https://chromium-review.googlesource.com/1115573
Reviewed-by: [email protected] <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#539}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Revert "[PE] Reland: Force backgrounds to fill to the border"
This reverts commit 8430ff876f5da79f02ac1de280d00f52f22d03bc.
Reason for revert: breaks background-position with percentage lengths
and large sprite maps. http://crbug.com/825239
This is a manual revert that only covers some portions of the change.
Also adds a test for the case that was broken.
Original change's description:
> [PE] Reland: Force backgrounds to fill to the border
>
> Background geometry calculations snap the background painting
> differently to the way borders snap. This patch forces the background
> to match the border whenever possible.
>
> In addition to the new test, our existing zoomed SVG-as-image tests
> also improve (they previously did not fill to their border). Some sprite
> background tests regress a little. They will be fixed by other
> forthcoming changes to background painting.
>
> Also factor the positioning area computation out of the primary
> Calculate method.
>
> [email protected]
> BUG=716174
>
> Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
> Reviewed-on: https://chromium-review.googlesource.com/909450
> Commit-Queue: Stephen Chenney <[email protected]>
> Reviewed-by: Florin Malita <[email protected]>
> Cr-Original-Commit-Position: refs/heads/master@{#535823}
> Change-Id: I0165da6a4448e1452626fc0045011a8216ed33b4
> Reviewed-on: https://chromium-review.googlesource.com/913588
> Reviewed-by: Stephen Chenney <[email protected]>
> Cr-Commit-Position: refs/heads/master@{#536076}
[email protected]
[email protected]
(cherry picked from commit aae829ecb980744bfc0c69323da928775aca2b47)
Bug: 716174, 825239
Change-Id: Iaf972e6963bbc578b0600b295e679ae987a9a5cd
Reviewed-on: https://chromium-review.googlesource.com/1106517
Commit-Queue: Stephen Chenney <[email protected]>
Reviewed-by: Florin Malita <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568906}
Reviewed-on: https://chromium-review.googlesource.com/1115563
Reviewed-by: Stephen Chenney <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#538}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Initialize full hardware class properly.
Bug: 856378
Change-Id: I41ec3fb062184979105c20db48fbef485e5b365f
Reviewed-on: https://chromium-review.googlesource.com/1114469
Reviewed-by: Alexei Svitkine <[email protected]>
Commit-Queue: Jong Ahn <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#570471}(cherry picked from commit 21d4c7bb95dbc1e81d58215eacc680a926f249a6)
Reviewed-on: https://chromium-review.googlesource.com/1115519
Reviewed-by: Bernie Thompson <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#537}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Revert "Do not recover incognito tabs if user deliberately terminates Chrome."
This reverts commit 0928665a2f97833277504d979800bc45cc526da1.
Reason for revert: This behavior is causing more confusion for users than it is helping. See crbug.com/854274 for details.
Original change's description:
> Do not recover incognito tabs if user deliberately terminates Chrome.
>
> Previously incognito tabs were always recovered no matter how the app
> was last shutdown.
>
> Instead, do not restore the incognito tabs if the user explicitly closes
> Chrome. If the system terminates the app, the tabs should be restored.
> (This can happen at any time and without user notice, so such
> terminations should not lead to a loss of the user's incognito tabs.)
>
> Bug: 653248
> Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
> Change-Id: I018cdf5cda2004e32e1010c4d9bab4bd10c0ae99
> Reviewed-on: https://chromium-review.googlesource.com/835532
> Reviewed-by: Eugene But <[email protected]>
> Commit-Queue: Mike Dougherty <[email protected]>
> Cr-Commit-Position: refs/heads/master@{#526099}
[email protected],[email protected],[email protected]
# Not skipping CQ checks because original CL landed > 1 day ago.
Bug: 653248, 854274
Change-Id: I952db05d6364d0944c3e46b9fa78b1432e889830
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Reviewed-on: https://chromium-review.googlesource.com/1106777
Commit-Queue: Mike Dougherty <[email protected]>
Reviewed-by: Mike Dougherty <[email protected]>
Reviewed-by: Eugene But <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568603}(cherry picked from commit 47c34860b5756f66c1dd90b4e2003f422c62deae)
Reviewed-on: https://chromium-review.googlesource.com/1115518
Cr-Commit-Position: refs/branch-heads/3440@{#536}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Merge to M68: Make Blink control browser mouse capture for scrollbar drags
The current behavior to allow mouse input in the browser process to be
locked to a given RenderWidgetHost is to send all mouse input between a
MouseDown and a MouseUp to the same target. This is not in accordance
with spec, and causes some site breakage.
Whether a MouseDown should cause capture depends on the node that the
event hits. Drag-highlighting text or clicking the thumb part of a
scrollbar require capture, for instance, while most elements do not.
This change removes the implicit capture currently done in the browser,
and replaces it in the case of scrollbars with an explicit signal from
Blink to start capturing. Other cases requiring capture still need to
be implemented.
Bug: 647378, 849862
Change-Id: Ifc4b690c36927ed48edd2604d40742e130295dcf
Reviewed-on: https://chromium-review.googlesource.com/1099183
Commit-Queue: Ken Buchanan <[email protected]>
Reviewed-by: Daniel Cheng <[email protected]>
Reviewed-by: Ella Ge <[email protected]>
Reviewed-by: Alex Moshchuk <[email protected]>
Reviewed-by: David Bokan <[email protected]>
Reviewed-by: Navid Zolghadr <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#569740}
Reviewed-on: https://chromium-review.googlesource.com/1112757
Reviewed-by: Ken Buchanan <[email protected]>
Reviewed-by: Charlie Reis <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#535}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Modern] Revert close icon "always" shown as action on custom toolbar
On History/Download/Bookmarks, if we set close icon to "always" shown
as action, the other items can be collapsed into an overflow menu that
appears to the right of the close icon. We should temporarily set the
showAsAction back to "ifRoom" until we figure out a better way to
customize collapsing the items into an overflow menu.
[email protected]
Bug: 849849
Change-Id: Ic94f8d9071dc0295ec5adc10e36ab74eb4a2150b
Reviewed-on: https://chromium-review.googlesource.com/1114307
Reviewed-by: Theresa <[email protected]>
Commit-Queue: Becky Zhou <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#570277}(cherry picked from commit 2dcc61258b623969b900fd38bca45c61d709a782)
Reviewed-on: https://chromium-review.googlesource.com/1115438
Reviewed-by: Becky Zhou <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#534}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[PE] Fix repeating table header/footer printing when page is scrolled
[email protected]
(cherry picked from commit d1615ffa2f911b8d8582b02f1b15666fad3725b4)
Bug: 854848
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Id1cf7b09fc32141758792c26f805fb73a1f131cb
Reviewed-on: https://chromium-review.googlesource.com/1109500
Reviewed-by: Chris Harrelson <[email protected]>
Commit-Queue: Xianzhu Wang <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#569420}
Reviewed-on: https://chromium-review.googlesource.com/1115419
Reviewed-by: Xianzhu Wang <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#533}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Don't deref null page_scale_node pointer.
This CL contains a mitigation for the null pointer dereference that
is at the root of the associated bug. Once this mitigation is confirmed,
we'll request a merge to M-68.
[email protected], [email protected]
(cherry picked from commit a5d4dd4d0adaee59ca0bbb9556d98872115c514d)
Bug: 845097
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ibfffdbe95c5d3b0e340c053f71056d88d75af3ac
Reviewed-on: https://chromium-review.googlesource.com/1112483
Reviewed-by: James MacLean <[email protected]>
Reviewed-by: David Bokan <[email protected]>
Commit-Queue: James MacLean <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#569756}
Reviewed-on: https://chromium-review.googlesource.com/1115351
Cr-Commit-Position: refs/branch-heads/3440@{#532}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Re-enable Scroll Anchor Serialization
Now that root layer scrolling and scroll anchoring are on unconditionally,
it no longer makes sense to check FrameView's ShouldPerformScrollAnchoring.
This inadvertently turned ScrollAnchorSerialization off even when the flag
was turned on.
Change-Id: I56f5224bb2aef6d06e4d0086b76a6122d4ac4ad3
Reviewed-on: https://chromium-review.googlesource.com/1100068
Reviewed-by: Steve Kobes <[email protected]>
Commit-Queue: Patrick Noland <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#567149}(cherry picked from commit 1702b04825afe60a2256a9ab242a21fa7ea1c8ef)
Reviewed-on: https://chromium-review.googlesource.com/1115378
Reviewed-by: Patrick Noland <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#531}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Roll SwiftShader cbb80f5..f398044
https://swiftshader.googlesource.com/SwiftShader.git/+log/cbb80f5..f398044
BUG=chromium:849217
Change-Id: Icdb69767175077f2c5712928217bf1767c10d90f
Reviewed-on: https://chromium-review.googlesource.com/1115210
Reviewed-by: Alexis Hétu <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#530}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Feature flag to launch the audio service on the browser startup.
Audio process experiment is observing performance regressions caused by
on-the-flight audio process launch. Introducing a feature flag to
pre-launch it on the browser startup.
This will be rolled out as another AudioService experiment group, to
evaluate memory and performance impact.
TEST=manual
Bug: 851611,853781, 856672
Change-Id: I30c1798dae07c5ce8a71243ab482ceb89d008e43
Reviewed-on: https://chromium-review.googlesource.com/1104681
Commit-Queue: Olga Sharonova <[email protected]>
Reviewed-by: Gabriel Charette <[email protected]>
Reviewed-by: Kinuko Yasuda <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#568389}(cherry picked from commit c0c0d24f28cef4117e92c146a89c97703401e866)
Reviewed-on: https://chromium-review.googlesource.com/1115318
Reviewed-by: Olga Sharonova <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#529}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Autofill] Only show autocomplete console warnings if we recognize the type.
[email protected]
(cherry picked from commit 7f47dadcb89ffe5da2c1520ccb94f9872b108fde)
Bug: 849658
Test: FormCacheTest
Change-Id: I5b32002958179b18491269aea874ec462266c0d9
Reviewed-on: https://chromium-review.googlesource.com/1086984
Commit-Queue: Mathieu Perreault <[email protected]>
Reviewed-by: Sebastien Seguin-Gagnon <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#564615}
Reviewed-on: https://chromium-review.googlesource.com/1115201
Reviewed-by: Mathieu Perreault <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#528}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
cros: Fix applist context menu execution histograms
These histograms were broken before the M68 branch. The code was
refactored after the branch, and the bug was fixed in M69.
This cl fixes the same bug fixed in M69, but avoids the
refactored part to minimize code changes.
Bug: 846370
Change-Id: I9479157ec3db46bcde29b2d4272e62a977393085
Reviewed-on: https://chromium-review.googlesource.com/1114225
Reviewed-by: Mitsuru Oshima <[email protected]>
Reviewed-by: Yury Khmel <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#527}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[Payments] Prevent nullptr dereference
Bug: 853950
Change-Id: I39129f9adb62ca3a0298fc20cb60751959e4ebdd
Reviewed-on: https://chromium-review.googlesource.com/1110343
Commit-Queue: Ganggui Tang <[email protected]>
Reviewed-by: Mathieu Perreault <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#569364}(cherry picked from commit bd205baa8b579ed20e4b9f51fe923390fc454494)
Reviewed-on: https://chromium-review.googlesource.com/1115018
Reviewed-by: Ganggui Tang <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#526}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
chrome://dino fix bug where the dino doesn't stop flashing.
Bug happens on the rare occasion that bdayFlashTimer == 0, the dino
keeps on flashing and bday mode never gets set.
Bug: 846473
Change-Id: Iddbe3f9fdba49c540930aac1721cb76a2b137af6
Reviewed-on: https://chromium-review.googlesource.com/1109501
Reviewed-by: Matt Menke <[email protected]>
Commit-Queue: Edward Jung <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#569247}(cherry picked from commit 9bfed9c22ad8283a2bbc60393440d009bc5c69dc)
Reviewed-on: https://chromium-review.googlesource.com/1114718
Reviewed-by: Edward Jung <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#525}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Switch to using features API instead of fieldTrialTests for enabling new
chrome://dino modes
Bug: 846473
Change-Id: I739b7e40e735da10cc7d7cd75cf808e770bf817e
Reviewed-on: https://chromium-review.googlesource.com/1100455
Commit-Queue: Edward Jung <[email protected]>
Reviewed-by: Matt Menke <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#567331}(cherry picked from commit cb482510098927c8b6b9306772d35cfa65e02000)
Reviewed-on: https://chromium-review.googlesource.com/1114698
Reviewed-by: Edward Jung <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#524}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
Add new mode for the offline dino easter egg
Bug: 846473
Change-Id: Iaf7e5d1153b7a78be5b2c2396d8baa9d34d5a306
Reviewed-on: https://chromium-review.googlesource.com/1085908
Commit-Queue: Edward Jung <[email protected]>
Reviewed-by: Matt Menke <[email protected]>
Cr-Original-Commit-Position: refs/heads/master@{#566064}(cherry picked from commit 693b9fcac0ff52f6653c0a27815d39fd077856a4)
Reviewed-on: https://chromium-review.googlesource.com/1114619
Reviewed-by: Edward Jung <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#523}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
M68 Reland "Remove blink::CallExtraOrCrash" (includes fixed)
This is functionally the same as the original cherry-pick
17254140a1f41e6057fcb22885c6178fa82affad but with compile fixes.
Also removed
virtual/outofblink-cors/http/tests/fetch/chromium/call-extra-crash-tee.html
and
virtual/outofblink-cors/http/tests/fetch/chromium/release-handle-crash.html
from SlowTests as these tests are not run in M68.
Original description:
CallExtraOrCrash is a function to call into V8 Extras and crash if it
fails. Unfortunately, calling into V8 Extras can fail under normal
conditions such as stack overflow and Worker destruction, causing a lot
of unnecessary crashes. Remove CallExtraOrCrash.
This is a stopgap change designed to be mergable to version 68. It
avoids major code restructuring but as a result lacks robust
encapsulation.
The general strategy is to pass a boolean pointer to functions in
ReadableStreamOperations that call into V8 Extras. If the internal call
fails, the boolean is set to true, and the call returns a default value.
BodyStreamBuffer keeps the boolean as member variable. Once a call to a
V8 extra function fails, the boolean is set and no more calls will be
made. This is to avoid us taking action based on information that is
incorrect.
For Tee() and the from-stream version of the BodyStreamBuffer
constructor, we use an ExceptionState object instead. In these cases, it
is straightforward to pass through ExceptionState object from the Blink
bindings. This allows the failure to be propagated safely back to
Javascript.
Conversely, DefaultReaderRead() has been switched from using
ExceptionState to using an error-signalling bool. This is because its
callers do not have access to a real ExceptionState object. Previously
callers used a NonThrowableExceptionState, but this was not suitable as
DefaultReaderRead() can throw.
BodyStreamBuffer mostly wraps access to ReadableStreamOperations, so
some degree of encapsulation has been retained.
7 new layout tests exercise each of the deterministically reachable
crashes, using stack overflows. Because they depend on stack layout and
whether DCHECKs are enabled, they only hit the crashes in particular
environments.
[email protected], [email protected], [email protected]
(cherry picked from commit 035ce793d12dbd436c609823f7160364110c9775)
Bug: 829790, 849312, 853977
Change-Id: I730a6c42da773afd9653bb2985916ffe92bb81c6
Reviewed-on: https://chromium-review.googlesource.com/1114404
Reviewed-by: Adam Rice <[email protected]>
Cr-Commit-Position: refs/branch-heads/3440@{#522}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}