Publish DEPS for 75.0.3770.90
Incrementing VERSION to 75.0.3770.90
TBR=kariah@chromium.org
Change-Id: I24465bf52b64b0aa4d3b9134c50d7d6b802104a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1653902
Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1003}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Release Platform Resources on WebCursor::operator=
On Windows, ui::PlatformCursor is just an HCURSOR. Creating a custom
cursor will create an HCURSOR with associated untracked GDI resources.
Then, an assignment at RenderWidgetHostViewAura::DisplayCursor will
overwrite the HCURSOR, leaking it.
This is problematic for web apps like Chrome Remote Desktop, which
needs to change the cursor on mouse entry/exit, leaking at every cursor
change.
This address a leak introduced by
https://chromium.googlesource.com/chromium/src/+/f95c2d9dd040c49b073d24b7ff69cfa94c1ff68c
through the removal of operator=, and a result, generating a default
assignment operator.
BUG=962392,960561
(cherry picked from commit 145c1fc192aeff0ea8fe20c9a9b147362dd26b56)
(cherry picked from commit 9ddfd4927133545624731c791e8db317f922f163)
Change-Id: I67878dbe285fc4ca1870f9676ed91d5c21b07d89
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1650298
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Auto-Submit: Robert Liao <robliao@chromium.org>
Cr-Original-Original-Commit-Position: refs/heads/master@{#667706}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1652365
Reviewed-by: Robert Liao <robliao@chromium.org>
Cr-Original-Commit-Position: refs/branch-heads/3821@{#3}
Cr-Original-Branched-From: 5529b8afe5f88f4af2bd20f664ef51a0d541b254-refs/heads/master@{#667630}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1653570
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1002}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Incrementing VERSION to 75.0.3770.89
TBR=govind@chromium.org
Change-Id: I1ff1344dbf7b3c2d23d41342b71bbf98a6e0416f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1652658
Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1001}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Stop clobbering/leaking a provisional main frame on window close.
The browser can not delete a speculative main frame that has committed
since the renderer takes ownership of it. This is a race since the
renderer makes this decision, and the browser may try delete it before
hearing it has been committed. In this case the renderer ignores the
delete to avoid losing state.
However as part of cancelling speculative navigation during shutdown,
the browser will also replace the RenderFrameProxyHost which makes a
RenderFrameProxy and RemoteFrame as the main frame in the renderer.
This is a problem because it replaces Page's main_frame_ pointer to
the main LocalFrame that was committed and not deleted by the
browser's request. The LocalFrame becomes an orphan that lives
indefinitely, with the LocalFrame and associated RenderFrame and
WebViewFrameWidget holding raw pointers back to the WebViewImpl,
the RenderWidget, and the RenderViewImpl. When these are closed
and destroyed, if the process is not killed entirely, the frame
will crash if it tries to access these.
Since WebContentsImpl drops all RenderFrameProxyHosts before destroying
the FrameTreeNode, we can not go through RenderFrameHostManager's
CleanUpNavigation() or DiscardUnusedFrame() as this path will recreate
the already deleted RenderFrameProxyHost, leading to the leaked frame.
So instead we can simply delete the speculative RenderFrameHostImpl
with UnsetSpeculativeRenderFrameHost(). This skips past recreating the
RenderFrameProxyHost, setting the speculative RenderViewHost as being
swapped out, and notifying in IPC that the nav was cancelled, none of
which should matter to do at shutdown.
TBR=avi@chromium.org, danakj@chromium.org, dcheng@chromium.org
(cherry picked from commit f9400609a167a8ef942a166bb7952daa8aa10627)
Bug: 964668, 838348, 915179
Change-Id: Icb7f2dfe6752ae745b0ea299fe4ca974b34516a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1648463
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: danakj <danakj@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#667139}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1652687
Reviewed-by: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#1000}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Fix gestures not being handled
It seems that when the compositor touch action is enabled, the way we
stop timeout monitor is incorrect. This results in two things:
1. Some of the pointer event are not getting acked and hence gesture
events are not handled correctly.
2. There are still quite a lot of gesture events getting timeout out.
In this CL, we have a temporary fix for problem 1 so that some of the
website can be fixed. Then we will have another follow up to solve
problem 2.
(cherry picked from commit 9daafa915a182bb172b8de9d2d88d8cc7223cb4f)
Bug: 971937, 971186
Change-Id: Id3ef77f0772c75895deb291323cd9cd45553204a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1650369
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#667725}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1653891
Reviewed-by: Ben Mason <benmason@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#999}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Reland "Reland "Handle race of SwapIn() and browser destroying the speculative MainFrame""
This is a reland of c32f307051fb3b2dec172efb901f18649d306db7
Original change's description:
> Reland "Handle race of SwapIn() and browser destroying the speculative MainFrame"
>
> This is a reland of e7d59816288ef3246defc4b86cb4e03e28d75956
>
> TestExpectations added for the portals test that is hitting crbug.com/838348
>
> TBR=avi@chromium.org, danakj@chromium.org, dcheng@chromium.org
>
> Original change's description:
> > Handle race of SwapIn() and browser destroying the speculative MainFrame
> >
> > When WebContentsImpl destroys, it deletes the speculative main frame,
> > but the renderer may have taken ownership of it already, and the notice
> > of such action is in flight to the browser still. This leads to DCHECKs
> > failing in the renderer. So inform the FrameMsg_Delete IPC what the
> > intention of the browser is, there are 3 modes:
> >
> > - Deleting a non-main frame. This is the common case. These frames are
> > all owned by the browser so it's all good, no races.
> > - Deleting a speculative main frame at shutdown. This is the race we
> > address here.
> > - Deleting a speculative main frame because it's no longer needed. This
> > race is not handled by this CL but we CHECK() it explicitly now instead
> > of letting the renderer continue with a missing RenderFrame that it
> > expects to be present until it crashes somewhere random later.
> >
> > TBR=avi@chromium.org, dcheng@chromium.org
> >
> > Bug: 957858, 838348
> > Change-Id: I2110bdaf8b116df48037f69db6cb992fa3796e29
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1594834
> > Commit-Queue: danakj <danakj@chromium.org>
> > Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> > Reviewed-by: Avi Drissman <avi@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#660025}
>
> (cherry picked from commit f23424355b6613cfdb70d34c7f75a7e7b75e9f04)
>
> Bug: 957858, 838348
> Change-Id: Iba424cc7be7db053c7ca617677b3cacf972fa067
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614132
> Commit-Queue: danakj <danakj@chromium.org>
> Reviewed-by: Lucas Gadani <lfg@chromium.org>
> Reviewed-by: Avi Drissman <avi@chromium.org>
> Cr-Original-Commit-Position: refs/heads/master@{#660128}
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639048
> Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Cr-Commit-Position: refs/branch-heads/3770@{#936}
> Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Bug: 957858, 838348
Change-Id: Ie7c21f16ddc77d39466a224077164f23721a1db2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1652655
Reviewed-by: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#998}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Reset bindings in DidDetachFrameView
We're already doing cleanup in this function, and with this change
we do our other cleanup here, too.
(cherry picked from commit 07fc424a8cb44bc98d27e52dc460fc861b290d7e)
Bug: 970252
Change-Id: I44748e1bef4941219d447ce22228816bf79dd963
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1645129
Commit-Queue: Ian Vollick <vollick@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#666713}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1652920
Reviewed-by: Ian Vollick <vollick@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#997}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
[ChromeDriver] Rename endpoints for accessing log
In W3C mode, replace non-standard /session/:sessionId/log* endpoints
with /session/:sessionId/se/log*, per agreement with Selenium.
(cherry picked from commit 0b81cefddc6b216fd6300eac855e39747f6f8767)
Bug: 973091, chromedriver:2947
Change-Id: I0c4b9833ace3e7ba5cb7ff0329f28041bf221da9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1652208
Commit-Queue: John Chen <johnchen@chromium.org>
Auto-Submit: John Chen <johnchen@chromium.org>
Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#667761}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1652505
Reviewed-by: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#996}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
[ChromeDriver] Allow POST with empty body in OSS mode
W3C WebDriver spec requires POST request to always have a non-empty
body. However, some legacy clients send empty POST body in some cases.
Updating ChromeDriver to handle such clients.
(cherry picked from commit e705a095439d0658fb81803396d4dcdb4c368c64)
Bug: 973088, chromedriver:2943
Change-Id: If29dd990dbebc0b4fc7c5df35ac25e4a4bc47f30
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1648893
Commit-Queue: John Chen <johnchen@chromium.org>
Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#667714}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1653588
Reviewed-by: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#995}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Do not send JavaScript results if they are not needed.
If large enough, they might OOM the IPC.
BUG=971688,972409
(cherry picked from commit 8e3ebe9c79594a3e0f00e5aac452f33a2ca1f2b6)
Change-Id: Icd25172270b1f111bd70b0d23c655d6d65c429d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1651058
Commit-Queue: Avi Drissman <avi@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#667732}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1653416
Cr-Commit-Position: refs/branch-heads/3770@{#994}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
[Touchless]: Return backup icon if no icon is available for context menu
(cherry picked from commit 0063e7a725af029c3009b13b25895119a9d27b44)
Bug: 970373
Change-Id: I6316993dfa21e73ea5b6e6b46186d4f4c576aab2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1652082
Commit-Queue: Cathy Li <chili@chromium.org>
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#667743}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1653411
Reviewed-by: Cathy Li <chili@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#993}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
[Touchless] Don't show PWAs on the last tab button
We can detect if a site in Chrome history is from a PWA launched
through webapk by:
* Constructing an intent with the URL of the site.
* Using the queryIntentActivities method to check what intents
launched the given URL.
* Check if the intents that launched the URL have the webapk class
name "org.chromium.webapk.shell_apk".
(cherry picked from commit 48877c8a1a8c7754ce664feaeed4bb6a349c0a06)
Bug: 968570
Change-Id: Ia3a51976f1876d3f21cddaf8c3ee34e34cee6f94
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1646138
Commit-Queue: Brandon Wylie <wylieb@chromium.org>
Reviewed-by: Pavel Yatsuk <pavely@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#666803}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1650639
Reviewed-by: Brandon Wylie <wylieb@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#992}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
[Touchless] Add "Remove" context menu item for last tab button
Selecting remove will remove last navigation from history and switch
last button to Google logo.
The logic is implemented by remembering timestamp of last removed
history entry in SharedPreferences. Only History items with later
timestamp are displayed on last tab button.
BUG=959317
R=wylieb@chromium.org
(cherry picked from commit bdb43101052c68f1056d7f211d5777bfee507d3b)
Change-Id: I8e67afca631bbc233d90f34791eff146bc1f37dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1644155
Reviewed-by: Brandon Wylie <wylieb@chromium.org>
Commit-Queue: Pavel Yatsuk <pavely@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#666044}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1653292
Reviewed-by: Pavel Yatsuk <pavely@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#991}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
[Touchless] Remove bottom padding from list of options in touchless dialog.
This change removes whitespace between list items and bottom navbar.
Screenshot before (with old styling): http://screen/BMAx13oRGeP
Screenshot after: http://screen/4RB0K6kaYTX
BUG=959317
R=mdjones@chromium.org
(cherry picked from commit e670f77e60808b28ca7458404648851979ec47a2)
Change-Id: I33927472dbb7c04639c80dd4314e388a92bd39a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639352
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Pavel Yatsuk <pavely@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#665679}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1653310
Reviewed-by: Pavel Yatsuk <pavely@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#990}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
[Touchless] Context menu for "Last tab" button
In this CL I only add "Add to my apps" item. Remove will be handled by
separate CL.
BUG=959317
R=wylieb@chromium.org
(cherry picked from commit fc3d63a11c6b3e80c37f54d953cd048f1c7c5918)
Change-Id: Idc200d40c3a704b78f5a733485f037819d591dd6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639521
Reviewed-by: Brandon Wylie <wylieb@chromium.org>
Commit-Queue: Pavel Yatsuk <pavely@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#665342}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1653309
Reviewed-by: Pavel Yatsuk <pavely@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#989}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
[Touchless] Add context menu to "More" button on NTP
BUG=959317
R=skym@chromium.org,mdjones@chromium.org
(cherry picked from commit 20db613a72f31b139963764a8678583d74603310)
Change-Id: Icb49eaac8aed5f66fbe16d12d615bb1f8567bbaa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636854
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Reviewed-by: Sky Malice <skym@chromium.org>
Commit-Queue: Pavel Yatsuk <pavely@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#665007}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1651080
Reviewed-by: Pavel Yatsuk <pavely@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#988}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
[Signin][Android] Disable sign-in promos if MobileIdentityConsistency is on
Adds to SigninManager.isSigninSupported a check for
MobileIdentityConsistency feature to hide sign-in UI surfaces if the
feature is enabled.
TBR=bsazonov@chromium.org
(cherry picked from commit b417842184890835c62f61c61a8314857bab39db)
Bug: 968140
Change-Id: I39156d4baf852d65117380bf98a983830d61dd6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1645308
Auto-Submit: Boris Sazonov <bsazonov@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Commit-Queue: Boris Sazonov <bsazonov@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#666349}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1651809
Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#987}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Fix ScrollFocusedEditableIntoView for selections
This method is used to scroll and zoom an editable element into view and
to a legible scale. This generally happens on Android where the
on-screen keyboard appears and the input box is zoomed into the
viewport.
The linked bug occurs because we try to zoom the input box while it has
a selection (e.g Ctrl-A the text) rather than a blinking caret. This
method would then receive an empty rect for the caret_rect which would
cause us to zoom into the maximum possible scale.
The fix here is to fallback to the selection rect if there is no carret.
(cherry picked from commit c5b24f8cb108411a0588b189742cee9b939a7675)
Bug: 968638
Change-Id: I980183bf9843192e694579cf2af4af816b78a090
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642248
Reviewed-by: Stefan Zager <szager@chromium.org>
Commit-Queue: David Bokan <bokan@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#666493}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1653070
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#986}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
media/gpu/v4l2/SupportResolutionChecker: Create only if codec is VP8 and decoder
SupportResolutionChecker is always created because of its Create() bug.
It must be created only for VP8 decoder on go2001 driver device.
(cherry picked from commit 96034b163e6b3e2e1c7ddb9b761ea4cb56c98ab8)
Bug: b:131366944, 971273
Test: tast run video.DecodeAccelH264 on hana
Change-Id: I174f5b1920e06bb578cb52e9ab636666f652c556
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1646809
Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#666650}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1647612
Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#985}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
media/gpu/V4L2VideoDecodeAccelerator: Raise PLATFORM_FAILURE if the resolution is unsupported
The maximum resolution supported by guado is 1080p in video decoding. HW decoder
on guado (V4L2VideoDecoder) won't raise an error when the initial resolution
(e.g. 2K video) is unsupported. It causes chrome to not fallback and make 2k
video decoding undoable. This CL adds workaround to V4L2VideoDecoder for this
issue. It parses every vp8 encoded frame, checks the resolution on key frame and
invokes NotifyError() if the resolution is unsupported.
(cherry picked from commit aa95d92bdf80bcfa94dcfce56251c0e3035d4721)
Bug: b:131366944
Test: run video_decode_accelerator_unittest on guado with 2K video file and get NotifyError
Test: 2K video can be seen on guado
Change-Id: Ic1ba2fa4a281dee6953d1696f991681217364f2b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637001
Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#665508}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1650542
Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#984}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
Incrementing VERSION to 75.0.3770.88
TBR=mmoss@chromium.org
Change-Id: I33fa68e7195dbd1552a3b8099dd417936acf59fb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1652648
Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/branch-heads/3770@{#983}
Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}