Publish DEPS for 75.0.3770.100
Incrementing VERSION to 75.0.3770.100
TBR=mmoss@chromium.org
Change-Id: Ia7d0bff2aad4dd8a1b5ee3dba3d2715c18fbed16
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1662852
Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1033}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
[SpatNav]: Make {cursor: pointer} trees focus candidates
Background:
Some web apps use one "catch all"-click handler, often put
on <body> or a container <div>, to react on clicks within
certain areas of the page. These web pages expect clicks
(or touches) and are not designed with key[board] users in
mind (they lack tabindex).
These pages' clickables, for example <div>s that look like
buttons, are often styled with {cursor: pointer}.
Problem:
These web pages are inaccessible for keyboard-only users.
Solution:
Enable SpatNav on these web apps by adding {cursor: pointer}
sub trees' tip to the list of navigation candidates.
Spec discussion:
https://github.com/w3c/csswg-drafts/issues/3395
Note:
snav-imagemap-area-not-focusable.html found a bug in
Chrome's UA CSS. We used to style *all* <area>s as
clickables, with {cursor: pointer}, even those without a
href-attribute. I fixed this in crrev.com/c/1653009.
(cherry picked from commit 308a30020307ae3925507536c48e5450c55b21f2)
(cherry picked from commit b2f29c71262890c28fbd7fdee139ba9af5c4a9ee)
Bug: 961927
Change-Id: I7baa2ba6f5f36ebc23b072d677edc66acfb2a70b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632231
Commit-Queue: Hugo Holgersson <hholgersson@fb.com>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Original-Original-Commit-Position: refs/heads/master@{#669193}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1662868
Cr-Original-Commit-Position: refs/branch-heads/3809@{#375}
Cr-Original-Branched-From: d82dec1a818f378c464ba307ddd9c92133eac355-refs/heads/master@{#665002}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1662837
Cr-Commit-Position: refs/branch-heads/3770@{#1032}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Fix for nullptr crash in SpatNav
No test since I don't know how to setup this situation. However, it's
safe to just avoid scrolling in this case.
(cherry picked from commit 3438927c32a922d35ea49c340fbbdb4c0c36bca9)
Bug: 970164
Change-Id: Icbae6b631e2f80e9e6493825fefb0f10fab974f6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1645792
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Commit-Queue: David Bokan <bokan@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#667579}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1662817
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1031}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Further qualify low end graphics optimizations
These can result in visual artifacts, so we should only
apply them where the memory impact is worth the
tradeoff.
(cherry picked from commit 7a847a8327a1e22dc83107dda61a50a3ca729682)
Bug: 974241
Change-Id: I771f0e919956eb3f677623989d7ac23bbb0ecc0e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1659940
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Eric Karl <ericrk@chromium.org>
Commit-Queue: Ian Vollick <vollick@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#669338}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1662831
Reviewed-by: Ian Vollick <vollick@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1030}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
[Signin] Pass externalCcResult to multilogin requests
Pass externalCcResult in the multilogin params to make sure it correctly
sets cookies for secondary domains.
This had conflicts with https://crrev.com/c/1572131 which were resolved
manually.
TBR=bsazonov@chromium.org
(cherry picked from commit 0aec7c82277205ddd4bf8e8a3a6604fe186d5019)
Bug: 971393, b/133516269
Change-Id: Iab7d6779e8137fd677e19929113464aa3acd9be6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1658572
Commit-Queue: Mihai Sardarescu <msarda@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#669320}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660334
Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1029}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Introduces a workaround for a hung that occurs when using autofill with accessibility
When Chromium automatically places an autofill suggestion in a text field, the value attribute of the text field does not update immediately.
Even though the value update should have been sent to the renderer, the accessibility tree on the browser doesn't update as soon as the autofill suggestion has been committed.
As a result, on Windows and Linux ATK, the text field's hypertext is empty, because it is retrieved directly from the text field's value.
However, the user-agent shadow DOM inside the text field contains a static text object with the autofill suggestion that has just been committed, whose hypertext is not empty.
When computing a parent equivalent position from an AXPosition after the static text object that represents the autofill suggestion, a position that is in the text field is correctly returned.
However, that position's text offset now holds a seemingly invalid value, because according to the hypertext of the text field, the field should contain no text.
This breaks all the comparison operators in AXPosition, because the above results in an infinit loop in the CompareTo method.
The proper fix is to update the hypertext of the text field in AXPlatformNodeBase to include the text of any autofill suggestion, (committed or uncommitted).
Alternatively the value attribute should be updated as soon as an autofill suggestion is committed.
However, both of this fixes are risky for M75.
A workaround has been introduced that tries to detect invalid text offsets in AXPosition::CreateParentPosition, and return a position at the start of the text node instead.
R=aleventhal@chromium.org, frpoole@microsoft.com
(cherry picked from commit d4b62c604f890e756a1cd71b2f3ec1816f1753d2)
Bug: 973722
Change-Id: I3786ee0cf9f0e9d83efc15c14702f242a8ba7851
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1661548
Auto-Submit: Nektarios Paisios <nektar@chromium.org>
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#669506}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1662710
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1028}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Incrementing VERSION to 75.0.3770.99
TBR=kariah@chromium.org
Change-Id: I0299a6563e3f8c7309e4842b53564e2f0470be14
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660843
Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1027}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Don't draw layer in kDstIn blend mode in resourceless software draw mode
Resourceless software draw mode doesn't support non-kSrcOver blend mode
if source is not a render surface. We should not draw in the case
because the fallback to kSrcOver would result a black mask on the
destination.
(cherry picked from commit 8540de427cab80ac0bf07ef57bae612e1b87d69c)
Bug: 973697
Change-Id: Ieaa9e612fe09512e925337ec131ced7594d64627
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1661289
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#669512}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1662498
Reviewed-by: Ben Mason <benmason@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1026}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Use IMM32 instead of TSF on Win10 RS2 and below.
This is a workaround for a bug in Windows Input Service. The bug is
fixed from Win10 version RS3 and above. It takes time for the fix to be
serviced for all downlevel Windows platforms. Alternatively, we can use
IMM32 instead of TSF on all affected platforms so that users won't hit
the crash immediately after this change.
(cherry picked from commit a16b6d1ec9239abf2c497db5595c1f7ca9ed9ffe)
Bug: 973329
Change-Id: I16d28091cf7699fa0563a610cc47d08989bc7951
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660961
Reviewed-by: Yohei Yukawa <yukawa@chromium.org>
Commit-Queue: Siye Liu <siliu@microsoft.com>
Cr-Original-Commit-Position: refs/heads/master@{#669525}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1661503
Reviewed-by: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1025}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Set link highlight effect to target opacity.
When the link highlight animation finishes, there is a race to remove
the link highlight node before it is renderered at full opacity. If the
finished function is not called in time we see the highlight blink.
Avoid this by setting the effect node to the end opacity.
(cherry picked from commit d03ff4b86983089940d824c98fd11b002c54752b)
Bug: 974160
Change-Id: I597629ee7457cc3bd77493ea87ed29e2916855fd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1661159
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Robert Flack <flackr@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#669431}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1662541
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1024}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Remove downstream NQE monitoring
This is no longer used and can be removed.
(cherry picked from commit e7918bac25137dcd0771e1df0ebeaf6bcd753603)
Bug: 974298
Change-Id: I485dffcc549e202bde603af75613e0803bb12f8a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660701
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#669353}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1661764
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1023}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Remove early exit from LayerTreeHost::AnimateLayers for BGPT
Running LayerTreeHost::AnimateLayers from the main thread is necessary
in order for the main thread KeyframeModels to progress from
WAITING_FOR_TARGET_AVAILABILITY to STARTING. Failing to advance to this
state results in the cc KeyframeModels never being removed as the
animation is still considered current and needing to affect the
pending tree.
(cherry picked from commit 93fe205c2143050ee45027cb1a3e926905373067)
Bug: 762717,962346
Change-Id: Ia559c0a7e3c73e12cc883e64fb4adb284a924418
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1256422
Commit-Queue: Robert Flack <flackr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#669075}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1662600
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1022}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Expose getTouchlessUiCoordinator from ChromeActivity
To be used by a downstream followup patch.
(cherry picked from commit 87a195f99482e93293935e630e2514baa5b856bf)
Bug: 974244
Change-Id: If225088e5dcd5401eeba4717b06702a36319efc6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1659981
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#669681}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1661761
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1021}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Ensure spat nav doesn't use an enter key press that was already used.
Some elements click on down or press, and spat nav clicks on up, so if
the down or press for an enter key event were handled, we shouldn't also
handle the up as a click.
(cherry picked from commit cdd0902ffcf59a4ecea78dc81d5a7751c37e30c7)
Bug: 973520
Change-Id: I2017da39b97d205e5dab4fa39c5b05e666e8677a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1656014
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#669314}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1662539
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1020}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Support form submission from spatial navigation.
When we get to the last non-submit-button element of a form the IME
action should change from Next to Submit.
(cherry picked from commit 18b921a22c85e88c3b7314b3ab8885281f48e5ca)
Bug: 968557
Change-Id: I5e61f184d30e6088fa80f3cdf95bbed1c344f46c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1648464
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#667156}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1661365
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1019}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Remove REQUEST_INSTALL_PACKAGES permission for notouch build
Downloads home isn't supported in notouch builds, so we don't need this
permission.
(cherry picked from commit 0e5c8a211005c4c94ce5bdd349abe9a6febe8f50)
Bug: 972750
Change-Id: I964dbfbc3c8d3a9d0be8b1b03884815a5d7c6bc6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1652055
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#667763}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1662019
Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1018}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
[css-flexbox] Make sure to layout overflow:auto elements
For overflow: auto, we need to layout before running the flex algorithm
if layout is dirty, so we can up-to-date scrollbar information, because
scrollbar size is included in the intrinsic size.
(cherry picked from commit 408ad4e0f177e8f6116963387576edd3f33c6e45)
Bug: 972227
Change-Id: I58b5c0590575c5babc505b2927d8464f3f540775
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1652198
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Auto-Submit: Christian Biesinger <cbiesinger@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#668199}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1662494
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1017}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
[M75 merge] Only honor base@target attributes for links and forms, as the spec requires
https://html.spec.whatwg.org/multipage/semantics.html#get-an-element's-target
(cherry picked from commit cb0fb84e7fd14a20ae9528ab0e3c8e8f9de33663)
Bug: 959973, 974197
Test: http/tests/navigation/location-navigate-iframe-with-base-target.html
Change-Id: Id49d355d41b75a9911365da6cb57e895d266fa72
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1599770
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Nate Chapin <japhet@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#657400}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660967
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1016}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
[blink] Clear loader client when script loads
Clear the response_body_loader_client field on ScriptResource when the
resource body finishes loading. This matches what the ResourceLoader
does, and removes a memory leak.
(cherry picked from commit 7a436bf3cf01b35073a70870b9d35ae07f876f19)
Bug: 944471
Change-Id: Icd2ef954c7f19624f4947a816882ef028321c95c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626858
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Leszek Swirski <leszeks@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#662579}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1661659
Reviewed-by: Ben Mason <benmason@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1015}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Incrementing VERSION to 75.0.3770.98
TBR=mmoss@chromium.org
Change-Id: I6408e290e36b381d7ca8d4d3c15bb515f5c9f29f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1661257
Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1014}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Incrementing VERSION to 75.0.3770.97
TBR=cmasso@chromium.org
Change-Id: Ie527a108be180ed9bf233ae84d9b5e8e701f5c8f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1661549
Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1013}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Incrementing VERSION to 75.0.3770.96
TBR=benmason@chromium.org
Change-Id: I94c1bfb7c3699dc18772e6496497cd58cb2fdcba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660270
Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1012}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
[Touchless]: Update center apps icon title from "All apps" to "Explore apps"
(cherry picked from commit 656e94d7bb292f2f2421cd3d355f71f445a1994a)
Bug: 974122
Change-Id: Ia4ce2d08fc5c6952864ed2667db1bbe03e5ab863
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660019
Reviewed-by: Sky Malice <skym@chromium.org>
Commit-Queue: Cathy Li <chili@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#669282}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660186
Reviewed-by: Cathy Li <chili@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1011}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Support ad block infobar for touchless
TBR=mdjones@chromium.org
(cherry picked from commit f54b27814f5656232ecae5fc5bd5486963cd6a0f)
Bug: 973550
Change-Id: I65db611c07f035d657db1b54de12fe82df347762
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1656468
Commit-Queue: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#668559}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1659982
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1010}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Incrementing VERSION to 75.0.3770.95
TBR=cmasso@chromium.org
Change-Id: I5a7d0138e9c2f603dd2967fbc6a6f00604422ead
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1659710
Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1009}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Incrementing VERSION to 75.0.3770.94
TBR=govind@chromium.org
Change-Id: Iaf982a7ec3ada778cc5d8180cc22bbaeeb39e6bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1657252
Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1008}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Incrementing VERSION to 75.0.3770.93
TBR=govind@chromium.org
Change-Id: Idefaaef3980d3d1c65d6bf2e13220ee16da56d30
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1657249
Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/3770@{#1007}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Incrementing VERSION to 75.0.3770.92
TBR=govind@chromium.org
Change-Id: I6947c88d5cd520ba5d62dae9c3eb265557dd1804
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1656909
Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1006}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Enforce not launching apps via "open link in a new tab"
Previously "Open link in a new tab/window" via context menu would allow
the user to stay on the web, regardless of whether or not we have
installed apps that are good candidates (because of the url/intent
filters the app exposes) nor if such apps were marked as preferred
before.
This CL aims to fix a regression where the user would escape to an
installed app that was marked as preferred before (it can also be a
verified app) while trying to open a given url on a new tab/window.
new tab via context menu.
(cherry picked from commit a6245bb2d403fbfe8036315438cbc1efbe2dbd70)
Bug: 968616
Test: Manual checked yelp app is not opening while clicking open in a
Change-Id: I9ebc76eeef44e73b204b8ac28343643ef584d50d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1638144
Reviewed-by: Maggie Cai <mxcai@chromium.org>
Commit-Queue: David Jacobo <djacobo@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#665073}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1654353
Cr-Commit-Position: refs/branch-heads/3770@{#1005}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Incrementing VERSION to 75.0.3770.91
TBR=kariah@chromium.org
Change-Id: I08ceda35aa72c0351a49218d68fe6cff04093bf5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1654194
Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1004}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}