Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
  1. Publish DEPS for 75.0.3770.89
    
  2. 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}
    
  3. 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}
    
  4. 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}
    
  5. 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}
    
  6. 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}
    
  7. [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}
    
  8. [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}
    
  9. 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}
    
  10. [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}
    
  11. [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}
    
  12. [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}
    
  13. [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}
    
  14. [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}
    
  15. [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}
    
  16. [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}
    
  17. 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}
    
  18. 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}
    
  19. 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}
    
  20. 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}
    
  21. Incrementing VERSION to 75.0.3770.87
    
    TBR=govind@chromium.org
    
    Change-Id: Id11c44ebcc8c6fcc1bc6614063a9a5821ee9de84
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1650625
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#982}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  22. Add Instrumentation to Inventory Tracked GDI Objects.
    
    A subset of GDI objects are tracked in the GDI Shared Handle Table.
    This change finds that table in the PEB and iterates through it,
    counting handle types that may be owned by the requested process.
    
    BUG=962392
    TBR=gab@chromium.org
    For BUILD.gn changes.
    
    (cherry picked from commit 58bb1db3f8586ca4a48d772917572b79850fff5e)
    
    Change-Id: I83e9138e4d8e83dba3d086057b0ae0f12daa034b
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1650405
    Commit-Queue: Robert Liao <robliao@chromium.org>
    Reviewed-by: Will Harris <wfh@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#667416}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1651102
    Reviewed-by: Robert Liao <robliao@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#981}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  23. Incrementing VERSION to 75.0.3770.86
    
    TBR=cmasso@chromium.org
    
    Change-Id: I5c6b6fe3803e25a1c223602d02754f2fd28ae36e
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1650237
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#980}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  24. Incrementing VERSION to 75.0.3770.85
    
    TBR=abdulsyed@chromium.org
    
    Change-Id: I790ac4be30487029c1d38153482242ed743aa685
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1650609
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#979}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  25. M75 merge [ios] Fix crash in page placeholder
    
    WebState::WasShown() is called even when the webState's view is
    not being presented. For example, this can happen during clear
    browsing data when the BVC is deactivated and activated. That
    is described in crbug.com/971364.
    
    Due to the complexity and ambiguity of BVC's |-setActive:| method,
    it is not modified in this CL. Instead, a lower risk approach is
    taken by not attempting to display the page placeholder if it is
    impossible to do so. The worst that can happen is that the page
    placeholder is not shown, which would not be that terrible to the
    user. This will prevent crashes seen in the real world.
    
    TBR=eugenebut@chromium.org
    
    Bug: 962843, 968096, 970876
    Change-Id: I00f68b78aff89aa154d0f98841310ab80723fe79
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1645479
    Commit-Queue: edchin <edchin@chromium.org>
    Reviewed-by: Eugene But <eugenebut@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#666761}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1650523
    Reviewed-by: edchin <edchin@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#978}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  26. [Touchless] Fix crash when clicking cookies toggle in settings
    
    This fixes a crash that was caused by tapping on the cookies toggle
    in site settings.
    
    (cherry picked from commit b4058c0028f0b20353e3d8c7d14d315302feed78)
    
    Bug: 968842
    Change-Id: I5e57f2e3f201500ce79d4bda4dc2bf2ae2456186
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1640803
    Reviewed-by: Finnur Thorarinsson <finnur@chromium.org>
    Commit-Queue: Mehran Mahmoudi <mahmoudi@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#665918}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1649412
    Reviewed-by: Ian Vollick <vollick@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#977}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  27. collapsed composition range should be considered as invalid.
    
    When user clicks outside editable region to terminate current ongoing
    composition, some IMEs may signal us with a collapsed composition range
    which length is 0. We should not consider it as a valid composition.
    
    TBR=siliu@microsoft.com
    
    (cherry picked from commit 99f31b2464612cc7e67afb57d8765b24e9ac1b3c)
    
    Bug: 966484
    Change-Id: I0351101b93b2f85536b841b2ba3721af2769d30a
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1638378
    Reviewed-by: Yohei Yukawa <yukawa@chromium.org>
    Commit-Queue: Siye Liu <siliu@microsoft.com>
    Cr-Original-Commit-Position: refs/heads/master@{#665594}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1648663
    Reviewed-by: Lan Wei <lanwei@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#976}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  28. Re-enable adding shortcuts in touchless mode.
    
    Fixes https://chromium-review.googlesource.com/c/chromium/src/+/1639639
    disabling shortcuts.
    
    (cherry picked from commit 75a4a11a85a1097d776613143e0a2fa48bd5de83)
    
    Bug: 972130
    Change-Id: I4947ba268586ee22832da795dea104be6a2f2b7b
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1649404
    Reviewed-by: Matthew Jones <mdjones@chromium.org>
    Reviewed-by: Theresa <twellington@chromium.org>
    Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#667270}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1649409
    Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#975}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  29. Updating XTBs based on .GRDs from branch 3770
    
    TBR=meacer@chromium.org
    
    Change-Id: I20197717946edd74bf8544e8839a0d7903a1f497
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1649708
    Reviewed-by: Krishna Govind <govind@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#974}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  30. Don't send any iframe navigations through NavigationScheduler
    
    This is a stripped down version of r655483 for merging to M75, focused
    on the fix and leaving out other cleanup from the original CL.
    
    (cherry picked from commit d1947e481162d5911ef5b11be11ee31237014919)
    
    Bug: 914587, 971641
    Change-Id: If74bbce23a7603cb8c826d1d7625584006b93322
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1525167
    Reviewed-by: Reilly Grant <reillyg@chromium.org>
    Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
    Commit-Queue: Nate Chapin <japhet@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#655483}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1648286
    Reviewed-by: Daniel Cheng <dcheng@chromium.org>
    Reviewed-by: Charlie Reis <creis@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#973}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  31. Incrementing VERSION to 75.0.3770.84
    
    TBR=mmoss@chromium.org
    
    Change-Id: I2af72f7fde92277b067a461af4b9dec8475434ec
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1649203
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#972}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  32. [Merge to M75] Update presentation time calculations.
    
    As per the spec, the driver is expected to return a valid timestamp from
    the call eglGetFrameTimestampsANDROID() when its not
    EGL_TIMESTAMP_PENDING_ANDROID or EGL_TIMESTAMP_INVALID_ANDROID.
    But currently few buggy drivers returns an invalid timestamp 0.
    
    We fix/workaround this in chrome by returning the presentation time
    as TimeTicks::Now() (snapped to the next vsync) instead of 0.
    
    (cherry picked from commit 7746363d083e6b3451a99199bf3a3be1040d3175)
    
    Bug: 966638
    Change-Id: I5075dda0739f02029922ebbc20c09656fb0e87ba
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631354
    Reviewed-by: Antoine Labour <piman@chromium.org>
    Commit-Queue: vikas soni <vikassoni@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#663918}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1648894
    Reviewed-by: vikas soni <vikassoni@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#971}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  33. Disable D3D11 on Intel drivers below 9.18.
    
    This is one of the earliest Intel driver versions we were comfortable allowing
    D3D11 on but it has issues with texture corruption when using the passthrough
    command decoder.
    
    BUG=941620
    
    (cherry picked from commit b7d5c33febdfb804bbe88d210c0e71b4b7ac2c21)
    
    Change-Id: I3ab49f81dbe74499d594ca5c29dea80d6cc9b5d6
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1645933
    Reviewed-by: Zhenyao Mo <zmo@chromium.org>
    Commit-Queue: Geoff Lang <geofflang@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#666420}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1648287
    Reviewed-by: Geoff Lang <geofflang@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#970}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  34. Restore accidentally removed null check. 
    
    A null check was removed due to a merge issue.
    It's the likely culprit for increasing crashes 
    in ToggleInlineSettings.
    
    Bug: 950121
    Change-Id: I04d408da968eb123bb7f50a2e2ba3a36ae7da69f
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1648281
    Reviewed-by: Vladislav Kaznacheev <kaznacheev@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#969}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  35. Incrementing VERSION to 75.0.3770.83
    
    TBR=govind@chromium.org
    
    Change-Id: I225ac99a0034afe3b14cde1fac167f812dd925ef
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1647189
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#968}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  36. AppCache: Reuse cacheable resources on cache update.
    
    (cherry picked from commit 4c91650bde69c7d0b7597295f38c93e272b0ddce)
    
    Bug: 968179
    Change-Id: Ib07f23f14102e9bfed5f54c9ccf9a35fffceb258
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636266
    Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
    Commit-Queue: Victor Costan <pwnall@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#665267}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1646650
    Reviewed-by: Victor Costan <pwnall@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#967}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  37. Update duplicate download infobar text on touchless
    
    TBR=mdjones@chromium.org
    
    (cherry picked from commit 6d57c0566481898310f18c6155b1556c0aa66337)
    
    Bug: 970270
    Change-Id: Ia2ebf2c17a0851f517ea355ac16228cf7a9e4024
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642952
    Reviewed-by: Theresa <twellington@chromium.org>
    Commit-Queue: Matthew Jones <mdjones@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#665987}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1647133
    Reviewed-by: Matthew Jones <mdjones@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#966}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  38. Management WebUI: Remove overview section details
    
    The overview detailed section string contained misleading text and had
    which has to be removed until a better alternative is found.
    
    Visuals:
    account managed: http://screen/TCtWNT44JTd
    Account + Device managed multiple domains: http://screen/nscXyUCZVP1
    Account + Device managed same domains: http://screen/2smNxaQj4eP
    device managed: http://screen/nr9wd8SRGqw
    Not managed: http://screen/G6Dh2a37nOU
    
    (cherry picked from commit 33f75bc37eab9aecd2ff5b69d193e64ec27fdc0c)
    
    Bug: 971263
    Change-Id: I5b2a66c4d6484024a60049b59dd78b0dfd287c07
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1645932
    Commit-Queue: Yann Dago <ydago@chromium.org>
    Reviewed-by: Scott Violet <sky@chromium.org>
    Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#666413}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1647112
    Reviewed-by: Yann Dago <ydago@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#965}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  39. Revert "Remove id of the release pointer before call to handle"
    
    This reverts commit 71b6a104210a6f64ed311d003e327753010b636d.
    
    Reason for revert: Fix a crash of issue 960234
    
    Original change's description:
    > Remove id of the release pointer before call to handle
    >
    > Bug: 874948
    > Change-Id: I9027567fcdefef414b8d261a546be8c0b1b979dc
    > Reviewed-on: https://chromium-review.googlesource.com/c/1491998
    > Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
    > Reviewed-by: Lan Wei <lanwei@chromium.org>
    > Reviewed-by: Scott Violet <sky@chromium.org>
    > Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
    > Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org>
    > Cr-Commit-Position: refs/heads/master@{#636564}
    
    TBR=lanwei@chromium.org, mustaq@chromium.org, nzolghadr@chromium.org, sky@chromium.org
    
    
    (cherry picked from commit ce43ead0563d0db9338844f71ac210d7d8597c98)
    
    Bug: 874948
    Change-Id: I84df52d9f1da640db2cf96afd109f9e9b692bd14
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1602280
    Reviewed-by: Lan Wei <lanwei@chromium.org>
    Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
    Commit-Queue: Lan Wei <lanwei@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#658209}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1646854
    Cr-Commit-Position: refs/branch-heads/3770@{#964}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  40. Updating XTBs based on .GRDs from branch 3770
    
    TBR=meacer@chromium.org
    
    Change-Id: I0a5596425c56120a5ab2033cd386a712a5b39465
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1645634
    Reviewed-by: Krishna Govind <govind@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#963}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  41. Respond to lifecycle events and periodcally refresh the last tab button
    
    * Periodically queries the history service and refreshes the last tab
      button.
    * Responds to tab events to refresh the last tab button.
    
    (cherry picked from commit 65bb962f8227d144c448cea113f57fa1816bb747)
    
    Bug: 959860
    Change-Id: Ib4f039c377211e8471267991442ff81318068867
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627895
    Commit-Queue: Brandon Wylie <wylieb@chromium.org>
    Reviewed-by: Sky Malice <skym@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#665278}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1645979
    Reviewed-by: Brandon Wylie <wylieb@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#962}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  42. [Bluetooth WinRT] Explicitly open GATT service for shared access
    
    It appears that GetCharacteristicsAsync() will implicitly open a GATT
    service for exclusive access. We don't want this so this change adds an
    explicit OpenAsync() call to choose shared access. The test fakes are
    updated to only support shared access.
    
    (cherry picked from commit cd0149afc87168562b233e6853ecec5f77a304eb)
    
    Bug: 968816
    Change-Id: I30af95fe428fad075ae8cbddd3075979a834e65f
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637192
    Reviewed-by: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org>
    Commit-Queue: Reilly Grant <reillyg@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#665005}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1645144
    Reviewed-by: Reilly Grant <reillyg@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#961}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  43. Show confirmation that a site/app was added on touchless
    
    TBR=mdjones@chromium.org
    
    (cherry picked from commit baf2ce496b5c56bc58acf7b92d7a57db64969e7c)
    
    Bug: 969204
    Change-Id: I0f7c3d0a4dee0c6debd09ddc6ea67587dd744cbb
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639639
    Commit-Queue: Matthew Jones <mdjones@chromium.org>
    Reviewed-by: Theresa <twellington@chromium.org>
    Reviewed-by: Peter Kotwicz <pkotwicz@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#666032}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1645457
    Reviewed-by: Matthew Jones <mdjones@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#960}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  44. [M75 Merge] Don't overwrite CVC fields to Unknown even when no server data.
    
    When running the condition for the AutofillOffNoServerData feature,
    I added a check to see if Autofill's client-side heuristics were
    predicting a CVC field. If they do, then we won't overwrite the type to
    "Unknown", as that breaks the CVC filling flow when unmasking server
    cards via the CVC prompt.
    
    Testing:
    Added unit tests
    Manually tested on the problematic website.
    
    (cherry picked from commit e3acfb09902c23992c42ebeda79773e59ff7ba43)
    
    Bug: 968036
    Change-Id: I9fa010d148fd168bd8c0348e93e18edf903db88b
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636256
    Commit-Queue: Fabio Tirelo <ftirelo@chromium.org>
    Reviewed-by: Fabio Tirelo <ftirelo@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#664842}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1645732
    Reviewed-by: Sebastien Lalancette <seblalancette@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#959}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  45. Merge "XPath: Do not crash by a deep expression." to M75 branch
    
    The union defined in xpath_grammar.y should be on the stack.
    
    (cherry picked from commit 89afbe31dd09039cbe2ab744bd16031bba47ba3b)
    
    Bug: 961413
    Change-Id: I426ff2da51e0f3f678cb96ae97b80322e01c6b35
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1638207
    Reviewed-by: Kentaro Hara <haraken@chromium.org>
    Commit-Queue: Kent Tamura <tkent@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#665111}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1644505
    Reviewed-by: Kent Tamura <tkent@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#958}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  46. Incrementing VERSION to 75.0.3770.82
    
    TBR=mmoss@chromium.org
    
    Change-Id: I28ece43455054b1fa6463f4a1521026a76b51415
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1644459
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#957}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  47. [Merge] Navi: Add finch options for app and shortcut variation.
    
    (cherry picked from commit 0aa87c0b97c3aecf06fd7a43deeeae8ba9a5bfc2)
    
    Bug: 967785
    Change-Id: I12c99470ed982adee57dc5f73b109fda618ba379
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636275
    Reviewed-by: Jesse Doherty <jwd@chromium.org>
    Commit-Queue: Hector Carmona <hcarmona@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#664907}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643947
    Reviewed-by: Hector Carmona <hcarmona@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#956}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  48. Allow PWAs to handle opening suggestions from NTP/all apps.
    
    Restricting to NoTouchMode to lower riskiness/contentiousness of this
    change.
    
    (cherry picked from commit 124aa6a3e4a8d4768cd118efb9bb45ad4ee43efb)
    
    Bug: 968573
    Change-Id: I4b9247541179f8af0c0548d0d3bb6e6c05a0bba1
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637533
    Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
    Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#665195}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643325
    Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#955}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  49. [Merge to M75] Fix renderer kills when a process dies in the middle of a cross-site navigation.
    
    This CL fixes a process model bug which resulted in an attempt to
    reuse the current process for cross-site navigations if
    the current frame's process died after starting the navigation but
    before receiving the response.  The problem was in an
    IsRenderFrameLive() check in GetSiteInstanceForNavigationRequest(),
    which incorrectly led to picking the current SiteInstance in this
    case.
    
    This check was introduced in r377920 but it's not clear if there was a
    reason for adding it.  This CL removes it.
    
    (cherry picked from commit 77beeff977b49c6ab403747abd386ec7379c85d2)
    
    Bug: 968259
    Change-Id: Ibf0dd6a6b6bf0c3a8c9192a2225ec2f5aa87c256
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1633591
    Commit-Queue: Alex Moshchuk <alexmos@chromium.org>
    Reviewed-by: Charlie Reis <creis@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#664497}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643350
    Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#954}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  50. Don't destroy members if TabGroupUI isn't initialized
    
    There may be cases where TabGroupUI is constructed and then destroyed
    wihtout calling initWithNative. This is a band-aid fix to address that
    and not attempt to destroy members that are not assigned yet. (The
    members are not individually checked to make the CL shorter, as we may
    need to cherry-pick)
    
    BUG=966769
    
    (cherry picked from commit 1895b3a2d9c8b75af5a02e73e8e20bc9d1b64235)
    
    Change-Id: I991c99c65d024e4115e327f6252810409e512951
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636456
    Reviewed-by: Pedro Amaral <amaralp@chromium.org>
    Commit-Queue: Yusuf Ozuysal <yusufo@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#664587}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643653
    Reviewed-by: Yusuf Ozuysal <yusufo@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#953}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  51. [Touchless] Implement new progress bar design
    
    This implements the new progress bar design for touchless.
    
    Screenshot of this implementation: http://crbug.com/958184#c21
    Mock: https://docs.google.com/presentation/d/1c-aVSZ_zsBuzCwQ4CrBJppmRQjiupa6PXmlC2OS-F-Q/edit?hl=en#slide=id.g5a1bc6d2c5_1_0
    
    (cherry picked from commit 1ec66a5886d7322515472ae041e5c0301cef8e02)
    
    Bug: 958069,958184
    Change-Id: I0b21876379036cd4aba3105c35345e187275a60c
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628869
    Commit-Queue: Mehran Mahmoudi <mahmoudi@chromium.org>
    Reviewed-by: Matthew Jones <mdjones@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#664927}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643727
    Reviewed-by: Ian Vollick <vollick@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#952}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  52. Add WilcoDtc feature flag
    
    Start WilcoDtcSupportdManager only if WilcoDtc feature is set.
    
    BUG=b:123926541
    TEST=local device
    
    (cherry picked from commit c02946d4d8c634703fba86f45ab0c4a5cfd0794f)
    
    Change-Id: I3caab04b1445c43b8a32e4a8ef1bfbbaa357b871
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1604275
    Commit-Queue: Polina Bondarenko <pbond@chromium.org>
    Reviewed-by: Dan Erat <derat@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#662563}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628608
    Reviewed-by: Polina Bondarenko <pbond@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#951}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  53. Incrementing VERSION to 75.0.3770.81
    
    TBR=govind@chromium.org
    
    Change-Id: I09a7c938aff84140eabb9e2c10e7277d25c1affc
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643648
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#950}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  54. [AW NS] Avoid redundant onDownloadStart callbacks when network service is disabled.
    
    MERGE to M75
    
    When the network service is disabled the Android WebView's
    DownloadListener.onDownloadStart() callback gets executed twice
    for the same url.
    
    This is due to the new code path (via AwDownloadManagerDelegate)
    which is intended to be executed when the network service is
    enabled is also run when it is disabled. This patch ensures that
    the new code path only runs when the network service is enabled.
    
    BUG=961264,841556
    
    (cherry picked from commit d456dd0bc299f6452852910c6ef51f2ba2bf8fc6)
    
    Change-Id: Ieec4a330d9d04173cf12ba23c90d9c37df08af47
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1638526
    Reviewed-by: John Abd-El-Malek <jam@chromium.org>
    Reviewed-by: Richard Coles <torne@chromium.org>
    Commit-Queue: Tim Volodine <timvolodine@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#665529}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643550
    Reviewed-by: Tim Volodine <timvolodine@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#949}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  55. Incrementing VERSION to 75.0.3770.80
    
    TBR=govind@chromium.org
    
    Change-Id: I6fd0d10746caf040ad78ef8b65a447327bd361d8
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642987
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#948}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  56. Revert "Reland "Handle race of SwapIn() and browser destroying the speculative MainFrame""
    
    This reverts commit c32f307051fb3b2dec172efb901f18649d306db7.
    
    Reason for revert: Introduces fun new crash in M75 beta. https://crbug.com/970040
    
    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}
    
    TBR=avi@chromium.org,danakj@chromium.org,dcheng@chromium.org,alexmos@chromium.org,lfg@chromium.org
    
    # Not skipping CQ checks because original CL landed > 1 day ago.
    
    Bug: 957858, 838348
    Change-Id: I1dfffcdb9691d166e57763df79f8520c850491a7
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1640831
    Reviewed-by: Daniel Cheng <dcheng@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#947}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  57. Add PolicyListMultipleSourceMergeList support for crOS
    
    (cherry picked from commit e00e7019418c85046b119760dc34a58b447f87ee)
    
    Bug: 969889
    Change-Id: I0df8a98a007691a2153b67caeaea3e22ea7ccadd
    TBR: pastarmovj@chromium.org
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1641988
    Commit-Queue: Yann Dago <ydago@chromium.org>
    Reviewed-by: Yann Dago <ydago@chromium.org>
    Reviewed-by: Owen Min <zmin@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#665672}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1641996
    Cr-Commit-Position: refs/branch-heads/3770@{#946}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  58. Incrementing VERSION to 75.0.3770.79
    
    TBR=cmasso@chromium.org
    
    Change-Id: I4cd5e92696fd7359a4df245fd480fedb8cb65ecf
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642155
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#945}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  59. Merge M75 "ash: Fix shelf bounds not updated with overview"
    
    > Shelf bounds update (e.g. from alignment change) during overview
    > animations is ignored and should be applied after the animations.
    >
    > Bug: 964910
    > Change-Id: I8d10de13954b5421c345a90ff601bafbe481cabe
    > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636566
    > Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
    > Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
    > Cr-Commit-Position: refs/heads/master@{#664933}
    
    (cherry picked from commit 9663fa3bb6c8883e68b2e1f8aeab00cc797a158a)
    
    Change-Id: Ic725f4692610b6c98a22ba8c00c1f5e3dfd451fb
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1642389
    Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#944}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  60. Remove the EnabledStateMonitorTest completely
    
    Bug: 945796
    Change-Id: I2036aff5584f5e3403c088d92875c78662772254
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639727
    Reviewed-by: Ben Mason <benmason@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#943}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  61. Incrementing VERSION to 75.0.3770.78
    
    TBR=govind@chromium.org
    
    Change-Id: I7e077a20960a5ee10628a28f65f7a112e76f863a
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1640599
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#942}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  62. Incrementing VERSION to 75.0.3770.77
    
    TBR=benmason@chromium.org
    
    Change-Id: I318d6bd87c7fee9bed3f9adcb09834f07183c036
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1640783
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#941}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  63. [Merge to 75] Force Enable Zoom should also override initial scale
    
    Merge Note: This merge contains 2 CLs, the second which fixes a defect
    in the first:
    
    53f9afcdecf35a8fb1e741d7cb9bfbd43b5f73c7
    Force Enable Zoom should also override initial scale
    
    c1eae0fa80520ccc58c01c722db6e2c2ba929c82
    Fix page scale limits override
    
    Force Enable Zoom should also override initial scale
    
    To understand why this is needed, note that the size of the layout
    viewport is calculated based on the minimum scale factor of the page.
    That is, we size the layout viewport to the size of the visual viewport
    when it's at the minimum allowable scale factor. |position: fixed|
    elements are sized relative to the layout viewport; therefore, their
    size depends on the minimum scale factor.
    
    When we override the minimum scale of a page, this can cause the layout
    viewport, and thus |position: fixed| elements, to increase in size. If
    we respect the initial-scale, this can cause fixed elements to appear
    cut-off by the viewport without a good visual indication to the user
    that zoom-out or horizontal scrolling is available. This is especially
    bad since the typical case here is a banner with a close [X] button at
    its far right. This causes those buttons to get cut out of view.
    
    
    Fix page scale limits override
    
    In https://crrev.com/53f9afcdecf35a8, we changed the Force Enable Zoom
    setting to also force reset the initial scale factor so that pages that
    specify an initial-scale in the viewport meta tag load fully zoomed out.
    
    Unfortunately, this caused the bug in 960518 since we always reset the
    initial scale factor to -1 when calling SetIgnoreViewportTagLimits. On
    AndroidTV devices the initial scale is overridden using
    SetInitialPageScaleOverride. This override would be clobbered when
    SetIgnoreViewportTagLimits was called (with false, to ensure the
    override is off).
    
    This CL fixes the issue by storing the user agent constraints when we
    override them, and resetting them to the original values when turning
    off the override.
    
    (cherry picked from commit 53f9afcdecf35a8fb1e741d7cb9bfbd43b5f73c7)
    
    Bug: 960518,929709
    Change-Id: Iacb6f6e92a5db11037710380e736f1f429575262
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1591888
    Commit-Queue: David Bokan <bokan@chromium.org>
    Reviewed-by: Ted Choc <tedchoc@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#656293}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1641422
    Reviewed-by: David Bokan <bokan@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#940}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  64. Incrementing VERSION to 75.0.3770.76
    
    TBR=kariah@chromium.org
    
    Change-Id: Ib2d1fcb74f45856fb9b7ccd04dff56f0a0a44971
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1638930
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#939}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  65. Incrementing VERSION to 75.0.3770.75
    
    TBR=benmason@chromium.org
    
    Change-Id: I1d94f1c4b0b07067193f9ef413ef4c31b203500f
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1638926
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#938}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  66. Incrementing VERSION to 75.0.3770.74
    
    TBR=cmasso@chromium.org
    
    Change-Id: Iaede141be9e3d9472d2a20d6b9b54ea76ca3d5ac
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639075
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#937}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  67. 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}
    
  68. [Merge M75] Fix build error in unit_tests
    
    Issue caused by bad merge conflict resolution in
    https://crrev.com/c/1638618 that left a header file out.
    
    Bug: 969190, 962558
    Change-Id: If50987037add8358a39495446a771819daaf5c74
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639331
    Reviewed-by: Kyle Milka <kmilka@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#935}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  69. [chrome.usb] Clear device on connection error
    
    When a USB device is disconnected Mojo connections to it are closed. The
    UsbDeviceResource object should listen for this connection failures and
    clear the InterfacePtr as otherwise calls are still allowed but their
    callbacks will never be executed.
    
    (cherry picked from commit 427c9aee17d70b7b3f36ee6f084fce23611087db)
    
    Bug: 968111
    Change-Id: I9e704b8b9bf0c067167374bb9910f83d566cdb7b
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636725
    Reviewed-by: Ken Rockot <rockot@google.com>
    Commit-Queue: Reilly Grant <reillyg@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#665029}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639497
    Reviewed-by: Reilly Grant <reillyg@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#934}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  70. Fix mailto links on ChromeOS with Network Service.
    
    When you navigate to a url with an unsupported scheme,
    NavigationURLLoaderImpl will attempt to open the URL with an external
    program. However, if you have a protocol handler associated with that
    scheme, it will handle the request in addition to the external program
    (see ProtocolHandlerThrottle).
    
    On ChromeOS, the external program ends up being a new tab, which then
    repeats this process and in certain situations can result in an infinite
    loop of tabs being opened. This CL prevents the browser from opening an
    external program if a protocol handler exists for the URL's scheme.
    
    A browser test will be added in a followup CL.
    
    (cherry picked from commit 1294d2484659aec6cbe86134074f575b55d0df76)
    
    Bug: 963133
    Change-Id: I6346b92adb3ea508a037b65a49dd1b44dd7d7b8f
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639077
    Commit-Queue: Robbie McElrath <rmcelrath@chromium.org>
    Reviewed-by: John Abd-El-Malek <jam@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#665249}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639134
    Reviewed-by: Robbie McElrath <rmcelrath@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#933}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  71. Reland "Change ICE connection state on transceiver changes"
    
    This reverts the revert
    https://chromium-review.googlesource.com/c/chromium/src/+/1636231
    which couldn't be reverted using "reland".
    
    Reason for reland: Flakiness seems to have been caused by leftover
    -expect files, not this patch.
    
    TBR=hbos@chromium.org
    
    (cherry picked from commit b05fc7151579ce23b02d3ac6cfff5ef231e97ce2)
    
    Bug: chromium:966798
    Change-Id: I450908dd3f49a8ae96bec2ba84c2812c40174e9d
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635811
    Commit-Queue: Harald Alvestrand <hta@chromium.org>
    Reviewed-by: Harald Alvestrand <hta@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#664669}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639007
    Reviewed-by: Srinivas Sista <srinivassista@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#932}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  72. PM: Cater for speculative RenderFrameHosts.
    
    Speculative RenderFrameHosts are not exposed in the content API, in e.g.
    WebContents::GetAllFrames. If speculative frames exist, and have been
    created at the time a PerformanceManagerTabHelper is attached to a
    WebContents, the TabHelper will learn of them at the first subsequent
    callback, which may e.g. be a deletion callback.
    This CL caters for those late notifications.
    
    (cherry picked from commit 62a9ad626f04492b9898c030e037929f4f2d9823)
    
    Bug: 948088
    Change-Id: I37aaa00f80f0e7d113f45798fcdc416680ddf0b3
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614755
    Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org>
    Commit-Queue: Chris Hamilton <chrisha@chromium.org>
    Reviewed-by: Chris Hamilton <chrisha@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#660508}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639437
    Reviewed-by: Patrick Monette <pmonette@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#931}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  73. Updating XTBs based on .GRDs from branch 3770
    
    TBR=meacer@chromium.org
    
    Change-Id: I17c9e0c16aa5f2e71fd4f2e91c562d46ec9ee373
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639139
    Reviewed-by: Krishna Govind <govind@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#930}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  74. AW NS: fix q-values for accept-language
    
    This fixes the Accept-Language request header when the Network Service
    is enabled by adding back q-values for language entry (to properly
    denote user preference).
    
    No change to legacy code path.
    
    (cherry picked from commit 1c5d4739676361db48f64a967d17f873a4b76f1d)
    
    Bug: 968287
    Test: out/.../bin/system_webview_shell_apk launch 'https://httpbin.org/headers' (verify header has q-values)
    Test: run_webview_instrumentation_test_apk --enable-features=NetworkService,NetworkServiceInProcess -f AcceptLanguageTest#*
    Cq-Include-Trybots: luci.chromium.try:android_mojo
    Change-Id: Ideb10bdf299505b40d96df8c771509a11c102ffc
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637451
    Reviewed-by: Changwan Ryu <changwan@chromium.org>
    Commit-Queue: Nate Fischer <ntfschr@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#664895}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1639177
    Reviewed-by: Nate Fischer <ntfschr@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#929}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  75. [omnibox] Merge max-URL-suggestions feature to 75
    
     [omnibox] Add flags for enabling and setting max URL suggestions
    
     This CL only adds a flag with parameter for enabling capping the
     number of URL suggestions, and configuring the limit.
    
     Bug: 963174
     Change-Id: I5d4310cf361dc5af1df734b8ff433720eef10fc0
     Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635435
     Commit-Queue: Kevin Bailey <krb@chromium.org>
     Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
     Cr-Commit-Position: refs/heads/master@{#664781}
     (cherry picked from commit cd6889928a0437fd4d1205f5ae7ab2bb884c012f)
    
     [omnibox] Experiment to limit the number of URL suggestions shown
    
     This CL adds a feature and companion parameter that respectively
     enable and select the preferred maximum number of URL suggestions to
     be shown in the Omnibox. The limit can be exceeded if there are no
     other types to replace them with.
    
     Bug: 963174 (not 966462)
     Change-Id: Id4a5e9cf5b5ef778f79de7f085e8bd5c7bfa779b
     Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628640
     Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
     Reviewed-by: manuk hovanesian <manukh@chromium.org>
     Commit-Queue: Kevin Bailey <krb@chromium.org>
     Cr-Commit-Position: refs/heads/master@{#664115}
     (cherry picked from commit b3e0873d64ad36628da36f8c26c29cb75ee51374)
    
    TBR=jdonnelly@chromium.org
    
    Bug: 963174
    Change-Id: I3226acf8dfede992df9efa9add25d1a65ffd715a
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1638780
    Reviewed-by: Kevin Bailey <krb@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#928}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  76. Incrementing VERSION to 75.0.3770.73
    
    TBR=cmasso@chromium.org
    
    Change-Id: I46c6bcdb08678b72f761d344d4546714abd63701
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637675
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#927}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  77. [omnibox] Merge group-by-search-vs-URL feature to 75
    
     [omnibox] Added flag for group by suggestion type feature
    
     This CL only adds a flag for a previously added feature: group
     suggestions by search vs URL.
    
     Bug: 966462
     Change-Id: I37d956baadad1a2bb5ea9968f4959933c0c61b2c
     Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631299
     Commit-Queue: Kevin Bailey <krb@chromium.org>
     Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
     Cr-Commit-Position: refs/heads/master@{#663809}
     (cherry picked from commit 38514f471cc28cc7bc057b29eaffa039534e1b8a)
    
     [omnibox] Rename flag
    
     This is just a follow-up to 1625811, to also rename the flag used to
     enable the feature, to OmniboxGroupSuggestionsBySearchVsUrl.
    
     Bug: 966462
     Change-Id: Id64c2751f105e9d57894a9f85f8307b1a687ff59
     Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626341
     Reviewed-by: Kevin Bailey <krb@chromium.org>
     Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
     Commit-Queue: Kevin Bailey <krb@chromium.org>
     Cr-Commit-Position: refs/heads/master@{#663122}
     (cherry picked from commit 38305596ee82eb4eb36b000381d01e158e3eb2eb)
    
     [omnibox] Experimental feature to group suggestions by type
    
     This implements an experimental feature (behind a flag) to group
     Omnibox suggestions by type, search results first, followed by other
     types, after the default match, which does not move.
    
     Bug: 966462
     Change-Id: I6870652be8f733b185ad1dcca946fb3091db0b09
     Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1625811
     Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
     Commit-Queue: Kevin Bailey <krb@chromium.org>
     Cr-Commit-Position: refs/heads/master@{#662749}
     (cherry picked from commit 0f7d159d4f2bf5a084a7abd8a4276fd7c6b72668)
    
    TBR=jdonnelly@chromium.org
    
    Bug: 966462
    Change-Id: Ibcdd006ed33245f1d86530618d5248d0e5906bef
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637668
    Reviewed-by: Kevin Bailey <krb@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#926}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  78. Whitelist usage of management.installReplacementWebApp
    
    This whitelists management.installReplacementWebApp to specific
    extensions as restrictions to ensure apps are related aren't yet
    implemented on the Webstore.
    
    For tests we need to generate manifest.json files based on the URL of
    the related app. Hence we can't check in a static crx/extension. This
    means that we need to provide a private key when generating the crx to
    ensure that the extension ID stays the same across test runs.
    
    TBR=raymes@chromium.org
    
    (cherry picked from commit 17ec7e69906c5818b071cdefdf13814c01230e81)
    
    Bug: 968407
    Change-Id: Ieceadeaf59011b7209fece3de06e89f2bea4b9e3
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635118
    Commit-Queue: Raymes Khoury <raymes@chromium.org>
    Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
    Reviewed-by: Ben Wells <benwells@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#665044}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636986
    Cr-Commit-Position: refs/branch-heads/3770@{#925}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  79. [Merge M75][NTP] Add Search tile to Most Visited tiles on the NTP
    
    On Desktop add a shortcut to the Google Search page to the
    list of most visited tiles if the user does not have
    custom links. If the user already has the maximum number
    of MV tiles the last one will be replaced with this new
    shortcut.
    
    (cherry picked from commit 9b07a92f88489c590d2b9ae8801fa2d702f636ab)
    
    Bug: 962558
    Change-Id: I6f3bf15f380cf02292ad738d65bf125c739dd68b
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1626955
    Reviewed-by: Steven Holte <holte@chromium.org>
    Reviewed-by: Marc Treib <treib@chromium.org>
    Reviewed-by: Cait Phillips <caitkp@chromium.org>
    Reviewed-by: Ramya Nagarajan <ramyan@chromium.org>
    Commit-Queue: Kyle Milka <kmilka@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#664875}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1638618
    Reviewed-by: Kyle Milka <kmilka@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#924}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  80. Remove EnabledStateMonitor enterprise tests
    
    Bug: 945796
    Change-Id: Ic0ef94988253364cf5dd9150c88ed21dfdc02e43
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1638140
    Reviewed-by: Theresa <twellington@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#923}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  81. Contents layer offset should be zero with ReplacedContentTransform
    
    ReplacedContentTransform bakes the offset into it, so the contents
    layer should have zero offset from transform node.
    
    TBR=wangxianzhu@chromium.org
    
    (cherry picked from commit cee067944c4fe30edaadf18e41f65c833501df04)
    
    Bug: 967652
    Change-Id: Iadfe3354286b9847acf41dd88822e40f73ccab64
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636601
    Reviewed-by: Philip Rogers <pdr@chromium.org>
    Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#664932}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1638660
    Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#922}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  82. Fix compile for WebAppDisplayModeTest
    
    Bug: 968957
    
    Change-Id: I30d722044263a4e3b6243558d933fb1c86523704
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637696
    Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#921}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  83. Reland "Only create AppsNavigationThrottle for main frame navigation."
    
    This is a reland of b0da5f749dba9cccdb07b387127106c842fe738c
    
    Original change's description:
    > Only create AppsNavigationThrottle for main frame navigation.
    > 
    > Currently we will create app navigation throttle for both main frame and
    > iframe navigations. This causes a issue where if there is a subframe
    > navigation it will overwrite the intent picker icon status that is
    > shown for the main frame. Previously a CL is landed
    > (https://chromium-review.googlesource.com/c/chromium/src/+/1609750) to
    > fix the issue by not showing the icon when there is a iframe. However if
    > a iframe navigation happens it will hide the icon even when the main
    > frame navigation request the icon to show. This CL fixs the issue and
    > adds tests for it.
    > 
    > BUG=964802
    > TBR=mxcai@chromium.org
    > 
    > (cherry picked from commit f51bb95784aa8d77ffad577fc26d960a0fcb47eb)
    > 
    > Bug: b/132641354
    > Change-Id: Ic7ce20daf4c7c7bd96eb48f112db2fd59214a14f
    > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1624073
    > Reviewed-by: Scott Violet <sky@chromium.org>
    > Reviewed-by: Dominick Ng <dominickn@chromium.org>
    > Commit-Queue: Maggie Cai <mxcai@chromium.org>
    > Cr-Original-Commit-Position: refs/heads/master@{#662904}
    > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636654
    > Reviewed-by: Maggie Cai <mxcai@chromium.org>
    > Cr-Commit-Position: refs/branch-heads/3770@{#905}
    > Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
    Bug: 964802, b/132641354
    Change-Id: I35c4326a5a9bcb020a32ee5ae2f7cad9702588f7
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1638197
    Reviewed-by: Maggie Cai <mxcai@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#920}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  84. Incrementing VERSION to 75.0.3770.72
    
    TBR=kariah@chromium.org
    
    Change-Id: Ie9d0e45ab53ccf693639b74fe19802b87ac7fae6
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1638143
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#919}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  85. gpu: Enable read lock fences on VAAPI pictures
    
    VaapiVDA reuses and decodes into buffers after they come back from
    clients.
    This patch sets a flag |read_lock_fences_enabled| on the Picture passed
    to VAAPI clients to make sure buffers won't be sent back until they're
    completely used by clients.
    This should prevent possible races where buffers are reused for decoding
    before their contents are fully displayed.
    
    (cherry picked from commit b3bd92598a8cc41eae9733e2af96e25c0d7ca8a9)
    
    Bug: 961411
    Test: Instructions in the bug
    Change-Id: I5584969f0c09b5b35584bf6f955b1a599b6ac0e9
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636453
    Reviewed-by: Dan Sanders <sandersd@chromium.org>
    Reviewed-by: Miguel Casas <mcasas@chromium.org>
    Commit-Queue: Daniele Castagna <dcastagna@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#664820}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637626
    Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#918}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  86. Revert "Remove default padding for cue text rendering"
    
    This reverts commit 6862f77d5ae1afb1e0606f6818e3a21eff3b8dc0.
    
    Reason for revert: bug 966345
    
    Original change's description:
    > Remove default padding for cue text rendering
    >
    > Per spec there is no default padding for text track cue rendering.
    > Removing the default padding for cue text.
    >
    > BUG=930608, 843136
    >
    > Change-Id: If931c1faff528a87d8a78808f30225ebe2377072
    > Reviewed-on: https://chromium-review.googlesource.com/c/1475567
    > Commit-Queue: srirama chandra sekhar <srirama.m@samsung.com>
    > Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
    > Reviewed-by: Fredrik Söderquist <fs@opera.com>
    > Cr-Commit-Position: refs/heads/master@{#633624}
    
    TBR=fs@opera.com, mlamouri@chromium.org, srirama.m@samsung.com
    
    
    (cherry picked from commit 131a5334945a231175a35f3841dafbd368795438)
    
    Bug: 930608, 843136
    Change-Id: If1183f0ef2b03f287b7ba562b4b45f5fff242b71
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628480
    Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
    Commit-Queue: Mounir Lamouri <mlamouri@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#663891}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636226
    Cr-Commit-Position: refs/branch-heads/3770@{#917}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  87. Adding files from a post-branch patch to grd to stop build failures
    
    Context:
    
    In an earlier post-branch patch [1] I added two new files, to the
    folder [2], namely [3] and [4]. In my original change on the master
    branch [5] I added the new files to the necessary .grd file [6].
    
    However, at the time of the M-75 branch, the "settings split" migration
    [7] was in an early stage and the new os-settings page's .grd file [8]
    was copied almost verbatim from the existing .grd file [6].
    
    Between that time and my change that added the new files [3] and [4],
    the migration removed several files from the new .grd file [8] because
    the os-settings page has no depedendence on them. In particular, when I
    added the new files [3] and [4] to the folder [2], there was no need to
    add them to the new .grd file [8] because all files that depended on
    [3] and [4] had been removed from [8] already.
    
    Therefore, when I merged the new change into M-75 in [1], the M-75
    version of [8] still contained files that would depend on [3] and [4]
    once [1] was merged even though [3] and [4] had never been added to
    [8], causing a build failure.
    
    Fix:
    
    This CL adds the files [3] and [4] to the new .grd file [8] and adds a
    "preprocess=true" argument to the files that have a dependence on [3]
    and [4] to process .html conditional tags because the dependences are
    all wrapped in a conditionals checking that the OS is CrOS.
    
    Testing:
    
    I used a set of gn args that caused a build failure on a current
    M-75 build (bd0529b42db02c71d24f4f77b637aba46792d5aa) but built and
    deployed successfully with this fix, working as intended on a dev
    Pixelbook.
    
    [1] https://chromium-review.googlesource.com/c/chromium/src/+/1632794
    [2] chrome/browser/resources/settings/autofill_page/
    [3] blocking_request_manager.html
    [4] blocking_request_manager.js
    [5] https://chromium-review.googlesource.com/c/chromium/src/+/1574684
    [6] chrome/browser/resources/settings/settings_resources.grd
    [7] http://crbug.com/950007
    [8] chrome/browser/resources/settings/os_settings_resources.grd
    
    
    Bug: 968328
    Change-Id: I2910c7ebd72a09a0ad3c73e2f49d1c451c5b651e
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637604
    Reviewed-by: May Lippert <maybelle@chromium.org>
    Reviewed-by: Geo Hsu <geohsu@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#916}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  88. Remove scroll bar on touchless dialogs
    
    TBR=mdjones@chromium.org
    
    (cherry picked from commit 19444b5ab445b0fde0b2b924e2f65609b030302d)
    
    Bug: 968566
    Change-Id: I48867b1c932d41c2654b9529fe41a86d8ab2bab6
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637504
    Reviewed-by: Matthew Jones <mdjones@chromium.org>
    Reviewed-by: Theresa <twellington@chromium.org>
    Commit-Queue: Matthew Jones <mdjones@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#664854}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637151
    Cr-Commit-Position: refs/branch-heads/3770@{#915}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  89. Allow use of fullscreen API from fullscreen PWAs
    
    Whatever issues caused us to initially disable the fullscreen API from
    fullscreen PWAs, they no longer seem to be present. In testing the
    sample in issue 720304 I couldn't find any issues.
    
    (cherry picked from commit edaef9cb38a9d012374d682e5c5bcdd7a2cbabb4)
    
    Bug: 963929
    Change-Id: I6fab2f4a558c2b7fdbd61b8ed92714f671bce7db
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627563
    Reviewed-by: Dominick Ng <dominickn@chromium.org>
    Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#664570}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636825
    Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#914}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  90. Pass the InputEvent to the dialog action Click handler.
    
    See bug for details.
    
    (cherry picked from commit 7dd284594c11a0d231978023844764fcf46fc766)
    
    Bug: 968332
    Change-Id: Iae95aa03dbb5b8841e0daebcafa51ec183d87b2a
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636477
    Reviewed-by: Matthew Jones <mdjones@chromium.org>
    Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#664742}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636822
    Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#913}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  91. Don't flag form submissions as client redirects for extensions use
    
    We have two subtly different definitions of a client redirect. One
    is exposed on the extensions webNavigation API, the other is used
    in headless mode and is based on whether a navigation used to go
    through NavigationScheduler. These definitions differ on whether
    form submissions should be client redirects. Enable each use case to
    see the definition it expects.
    
    (cherry picked from commit f83f9d5c495cfae0d43ffba5373ca797bb31c8e8)
    
    Bug: 960653
    Test: WebNavigationApiTest.FormSubmission
    Change-Id: If727762b7b5feef79e2e5059eddc75d57f982e08
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628158
    Commit-Queue: Nate Chapin <japhet@chromium.org>
    Reviewed-by: Daniel Cheng <dcheng@chromium.org>
    Reviewed-by: Nasko Oskov <nasko@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#663349}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636817
    Reviewed-by: Nate Chapin <japhet@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#912}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  92. [Merge M75][NTP] Fix LocalNTPSearchShortcutTest.SearchShortcutShown
    
    This test didn't work properly as it was waiting for the MV
    tiles to be initialized with a single default shortcut but
    if the feature is enabled there should be two default
    shortcuts.
    
    (cherry picked from commit 63fc525cd66b261c5232e51acf0375b1a7d6d637)
    
    Bug: 968073, 962558
    Change-Id: Id69c1c4c6748067eacd776550aa87cd160cf7656
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636391
    Reviewed-by: Ramya Nagarajan <ramyan@chromium.org>
    Commit-Queue: Kyle Milka <kmilka@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#664517}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637478
    Reviewed-by: Kyle Milka <kmilka@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#911}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  93. [Merge M75] Add default shortcut to Google Search on the NTP
    
    Add a flag to show a Google Search shortcut on the
    NTP by default. Only add the shortcut if this is
    a Chrome branded build.
    
    (cherry picked from commit 1f96bac05d78a91df4b58cc87c2406d33364ec15)
    
    Bug: 962558
    Change-Id: I4f5cd18b0dc3182264057f55eb381cb94d6ee49b
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614457
    Reviewed-by: Scott Violet <sky@chromium.org>
    Reviewed-by: Marc Treib <treib@chromium.org>
    Reviewed-by: Ramya Nagarajan <ramyan@chromium.org>
    Commit-Queue: Kyle Milka <kmilka@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#663980}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636558
    Reviewed-by: Kyle Milka <kmilka@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#910}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  94. Revert "Skip promoting SingleOnTop Overlay when contents don't change"
    
    This reverts commit b4fd0cc9d68915dd21d270a10e7cfd4eecc69919.
    
    Reason for revert: The Squid app uses SingleOnTop for overlay without changing the resource_id. This revert will undo the fix for the other apps, but they're lower priority.
    
    Original change's description:
    > Skip promoting SingleOnTop Overlay when contents don't change
    >
    > If a candidate content has not changed for 3 frames, do not promote it as
    > Single On Top overlay as it can be just be flattened, allowing other
    > strategies to kick in if possible.
    >
    > Bug: 885180
    > Test: SingleOverlayOnTopTest.DoNotPromoteIfPreviouslyPromoted
    > Change-Id: I516dab628c129fe9fae09c713e2783a6ce889c56
    > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1521591
    > Commit-Queue: Mark Yacoub <markyacoub@google.com>
    > Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
    > Cr-Commit-Position: refs/heads/master@{#645367}
    
    TBR=dcastagna@chromium.org,markyacoub@google.com
    
    # Not skipping CQ checks because original CL landed > 1 day ago.
    
    (cherry picked from commit f213924a9154f9080c2ac117207e545012acee26)
    
    Bug: 963056
    Change-Id: I799bd22f06a56d86844a63d5ac346f41bcfb8707
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635931
    Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
    Commit-Queue: Mark Yacoub <markyacoub@google.com>
    Cr-Original-Commit-Position: refs/heads/master@{#664734}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636930
    Cr-Commit-Position: refs/branch-heads/3770@{#909}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  95. Revert "Only create AppsNavigationThrottle for main frame navigation."
    
    This reverts commit b0da5f749dba9cccdb07b387127106c842fe738c.
    
    Reason for revert: The CL is causing build failures on continous beta builders
    
    Original change's description:
    > Only create AppsNavigationThrottle for main frame navigation.
    > 
    > Currently we will create app navigation throttle for both main frame and
    > iframe navigations. This causes a issue where if there is a subframe
    > navigation it will overwrite the intent picker icon status that is
    > shown for the main frame. Previously a CL is landed
    > (https://chromium-review.googlesource.com/c/chromium/src/+/1609750) to
    > fix the issue by not showing the icon when there is a iframe. However if
    > a iframe navigation happens it will hide the icon even when the main
    > frame navigation request the icon to show. This CL fixs the issue and
    > adds tests for it.
    > 
    > BUG=964802
    > TBR=mxcai@chromium.org
    > 
    > (cherry picked from commit f51bb95784aa8d77ffad577fc26d960a0fcb47eb)
    > 
    > Bug: b/132641354
    > Change-Id: Ic7ce20daf4c7c7bd96eb48f112db2fd59214a14f
    > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1624073
    > Reviewed-by: Scott Violet <sky@chromium.org>
    > Reviewed-by: Dominick Ng <dominickn@chromium.org>
    > Commit-Queue: Maggie Cai <mxcai@chromium.org>
    > Cr-Original-Commit-Position: refs/heads/master@{#662904}
    > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636654
    > Reviewed-by: Maggie Cai <mxcai@chromium.org>
    > Cr-Commit-Position: refs/branch-heads/3770@{#905}
    > Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
    TBR=sky@chromium.org,dominickn@chromium.org,mxcai@chromium.org
    
    Change-Id: I384f56d4c08f9e987161b59ab924321431b27700
    No-Presubmit: true
    No-Tree-Checks: true
    No-Try: true
    Bug: 964802, b/132641354
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637407
    Reviewed-by: Srinivas Sista <srinivassista@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#908}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  96. Incrementing VERSION to 75.0.3770.71
    
    TBR=abdulsyed@chromium.org
    
    Change-Id: Iafed472df10fe2fdb3e3b611df3c6846d2e279fd
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636342
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#907}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  97. Disable flaky CustomTabFromChromeExternalNavigationTest#testIntentWithRedirectToApp test
    
    This CL disabled the test only on Android K where it's flaky.
    
    (cherry picked from commit 66e0d91c539847a164d9a07bdd99756d2b967ce3)
    
    TBR: mvanouwerkerk@chromium.org
    Bug: 931198
    Change-Id: I66a1b2b785773c97afd806f064b9519315039a05
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636714
    Reviewed-by: Shimi Zhang <ctzsm@chromium.org>
    Commit-Queue: Shimi Zhang <ctzsm@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#664571}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1637401
    Reviewed-by: Ben Mason <benmason@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#906}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  98. Only create AppsNavigationThrottle for main frame navigation.
    
    Currently we will create app navigation throttle for both main frame and
    iframe navigations. This causes a issue where if there is a subframe
    navigation it will overwrite the intent picker icon status that is
    shown for the main frame. Previously a CL is landed
    (https://chromium-review.googlesource.com/c/chromium/src/+/1609750) to
    fix the issue by not showing the icon when there is a iframe. However if
    a iframe navigation happens it will hide the icon even when the main
    frame navigation request the icon to show. This CL fixs the issue and
    adds tests for it.
    
    BUG=964802
    TBR=mxcai@chromium.org
    
    (cherry picked from commit f51bb95784aa8d77ffad577fc26d960a0fcb47eb)
    
    Bug: b/132641354
    Change-Id: Ic7ce20daf4c7c7bd96eb48f112db2fd59214a14f
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1624073
    Reviewed-by: Scott Violet <sky@chromium.org>
    Reviewed-by: Dominick Ng <dominickn@chromium.org>
    Commit-Queue: Maggie Cai <mxcai@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#662904}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636654
    Reviewed-by: Maggie Cai <mxcai@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#905}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  99. Incrementing VERSION to 75.0.3770.70
    
    TBR=kariah@chromium.org
    
    Change-Id: I7a062582da6eaa5e78524b18daf976b3de4c9bb6
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636715
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#904}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  100. Only handle intent picker for main frame.
    
    Currently even when the navigation is happend in iframe, the apps
    navigation throttle will still check for apps that can handle the url
    and show in intent picker or launch the preferred app if there is one.
    This CL updates the code to check the nagivation before trying to handle
    intent picker.
    
    (cherry picked from commit 736f5023b7ea02acc162c954be96c688c773fb62)
    
    Bug: b/132641354
    Change-Id: I02901d89d6b56e0f91203df1cfe4d3a4d5f23c6a
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1609750
    Commit-Queue: Maggie Cai <mxcai@chromium.org>
    Reviewed-by: Dominick Ng <dominickn@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#659835}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1636653
    Reviewed-by: Maggie Cai <mxcai@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#903}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  101. [Merge to M75] Reland "Update Linux Seccomp syscall restrictions to EPERM posix_spawn/vfork"
    
    > This relands commit 65046b8f90d0336cbe5f2f15cc7da5cb798360ad,
    > plus an additional change:
    >
    > Older versions of Bionic seems to use vfork() in their system()
    > implementations, so just EPERM it instead of crashing with SIGSYS.
    >
    > Bug: 956644
    > Change-Id: Ibd84ca0a9c49cad3ba797a2632960f3978111c65
    > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1585108
    > Commit-Queue: Matthew Denton <mpdenton@chromium.org>
    > Reviewed-by: Tom Sepez <tsepez@chromium.org>
    > Cr-Commit-Position: refs/heads/master@{#657515}
    
    BUG=956644
    TBR=tsepez
    NOTRY=true
    NOPRESUBMIT=true
    NOTREECHECKS=true
    
    Change-Id: Idc32bc5940763114e86fe96a9a8820135022b367
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635360
    Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#902}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  102. Incrementing VERSION to 75.0.3770.69
    
    TBR=kariah@chromium.org
    
    Change-Id: I382a203840c38db4bb2334596cf664e8c0b95502
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635358
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#901}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  103. [CrOS Network] Fix network connection dialog in settings.
    
    The issue was trigged by a JavaScript error in getDialogTitle_(). This
    function attempts to evaluate |this.managedProperties_.Name| without
    checking whether |this.managedProperties_| is set.
    
    I added an early return to prevent against this case.
    
    (cherry picked from commit 190c678a1f538697f2df999d7cbadde7db2a35a6)
    
    Bug: 967807
    Change-Id: I14544a6185f255d73e405845446efb1fc07bf4dc
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1633213
    Auto-Submit: Kyle Horimoto <khorimoto@chromium.org>
    Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
    Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#664032}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634968
    Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#900}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  104. [Sync::USS] Fix missing bookmarks titles created from legacy entities
    
    (cherry picked from commit 1b62935fb7cb507d6338bffb622890e6d1d540f2)
    
    Bug: 967713
    Change-Id: I0fb0800c6d4fc3b114556f0ec70450a46eb18157
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632230
    Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org>
    Reviewed-by: Mikel Astiz <mastiz@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#663790}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635809
    Reviewed-by: Mohamed Amir Yosef <mamir@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#899}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  105. [Touchless] Add distillability singal for key functions IPH
    
    This adds a new signal that shows the key functions In-Product Help
    for websites that are not mobile-optimized.
    
    TBR=mahmoudi@chromium.org
    
    (cherry picked from commit 460d44601521c44ebbe77d08bf5463c58f4eba65)
    
    Bug: 942665
    Change-Id: I67b357973c23283f85e071b6e5d93a1e560a7001
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631350
    Commit-Queue: Mehran Mahmoudi <mahmoudi@chromium.org>
    Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#663615}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635438
    Reviewed-by: Matthew Jones <mdjones@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#898}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  106. Factor distillability signal into provider per-tab
    
    The distillability signal is useful for things other than reader mode.
    This patch factors out the use of DistillablePageUtils.setDelegate, a
    call that can only be made once per web content, into a tab helper.
    The new tab helper broadcasts the signal to observers that may be
    listening.
    
    This patch also includes a bit of cleanup of things like
    ReaderModeTabInfo.
    
    TBR=mdjones@chromium.org
    
    (cherry picked from commit 95a22beddebc6a2ad6d763412b7dae9f0fd53709)
    
    Bug: 942665
    Change-Id: I4b112a7aa7a2e17e57ff5a88df69a404ec205550
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1627821
    Reviewed-by: Theresa <twellington@chromium.org>
    Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
    Commit-Queue: Matthew Jones <mdjones@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#663291}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635290
    Reviewed-by: Matthew Jones <mdjones@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#897}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  107. Have the Recovery Tool use a UI message loop.
    
    This allows it to show dialogs and work as required.
    
    BUG=948882
    TEST=as in bug
    
    (cherry picked from commit 07bfa5914e8a8635cc265c6709dccf574f8f3d18)
    
    Change-Id: Ifc339187093e571f8f6062cfa4a9d3130a357e02
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1631873
    Auto-Submit: Avi Drissman <avi@chromium.org>
    Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
    Commit-Queue: Avi Drissman <avi@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#663764}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634933
    Reviewed-by: Avi Drissman <avi@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#896}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  108. Incrementing VERSION to 75.0.3770.68
    
    TBR=mmoss@chromium.org
    
    Change-Id: I662f8e57154971d0bea896509a25847e8e50c08c
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635409
    Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#895}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  109. wilco_dtc_supportd: log net error in PerformWebRequest
    
    Log a netwrok error if PerformWebRequest fails.
    
    BUG=b:133770869
    TEST=build
    
    (cherry picked from commit 03312d971b4c415e5755a9d08726d5e0c9581063)
    
    Change-Id: Iaa3f7dadc916fa184370b8dea769030f56aedb0e
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634693
    Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
    Commit-Queue: Polina Bondarenko <pbond@chromium.org>
    Auto-Submit: Polina Bondarenko <pbond@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#664250}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635250
    Reviewed-by: Polina Bondarenko <pbond@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#894}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  110. wilco_dtc_supportd: rollback the failing unit test
    
    network::TestURLLoaderFactory::IsPending is changed in M76, thus
    rollback the added unit test to avoid compilation errors.
    
    BUG=b:133733514
    TEST=unit_tests
    
    Change-Id: Ia1a47b632067efaa603d758e40ad54d5054401e4
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634855
    Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#893}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  111. [M75 Merge][Locked Fullscreen] Disable ChromeVox panel before entering locked fullscreen
    
    There's a P0 escape from the locked mode currently in M75 which is just days
    away from stable.  This is a very quick and simple fix that addresses the
    problem for now and it will be backmerged immediately to M75.
    
    TBR=isandrk@chromium.org
    
    (cherry picked from commit 93f458b056c5984627083083019a9d6fe475e8cd)
    
    Bug: 957950
    Change-Id: I2c39c04d4bc0219c000977928b538c60619a6bf6
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632251
    Commit-Queue: Ivan Šandrk <isandrk@chromium.org>
    Reviewed-by: Kush Sinha <sinhak@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#663763}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634871
    Reviewed-by: Ivan Šandrk <isandrk@chromium.org>
    Cr-Commit-Position: refs/branch-heads/3770@{#892}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}
    
  112. media: Add workaround for supported VAImageFormats in iHD.
    
    This CL adds a workaround for the advertised supported VAImageFormats in
    Intel's media driver (iHD). Right now, the driver is advertising some
    formats that it actually doesn't support. Until this is fixed, we are
    conservative and remove all the formats other than I420 or NV12 from the
    list of advertised formats.
    
    Some additional cleanup is done per https://crbug.com/956581.
    
    (cherry picked from commit 89ad17ce3c9acdd09d0e264ce1abd46767f97ef2)
    
    Test: VaapiJpegDecoderTest.* pass on eve.
    Bug: 955284
    Change-Id: I734581ef7c533251559c66355755d9e7766239cf
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1623491
    Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
    Commit-Queue: Andres Calderon Jaramillo <andrescj@chromium.org>
    Auto-Submit: Andres Calderon Jaramillo <andrescj@chromium.org>
    Cr-Original-Commit-Position: refs/heads/master@{#662201}
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634511
    Cr-Commit-Position: refs/branch-heads/3770@{#891}
    Cr-Branched-From: a9eee1c7c727ef42a15d86e9fa7b77ff0e63840a-refs/heads/master@{#652427}