Files
brave-core/app
Kamil JozwiakandClaudio DeSouza 63a044d0b0 Upgrade from Chromium 149.0.7827.23 to Chromium 149.0.7827.54. (#36858)
* Update from Chromium 149.0.7827.23 to Chromium 149.0.7827.54.

* [149.0.7827.54] Removes previously applied upstream patches.

* Update patches from Chromium 149.0.7827.23 to Chromium 149.0.7827.54.

* Updated strings for Chromium 149.0.7827.54.

* [149.0.7827.54] Stubbing off `OnEmbeddedPermissionPromptChanged`

Chromium changes:
https://chromium.googlesource.com/chromium/src/+/03d0729142a7f3db6bc6a16d69de16832cf32320

commit 03d0729142a7f3db6bc6a16d69de16832cf32320
Author: James Leung <jamesleung@google.com>
Date:   Thu May 14 22:43:43 2026 -0700

    [voice_search] Keep voice search open during permission prompt

    Modify the composebox voice search to remain active when an embedded
    permission prompt is displayed. This prevents the voice search overlay
    from timing out or closing while the user interacts with system access
    requests. An observer must be added to communicate via mojo to the
    frontend when the voice search should remain active.

    Key changes include:
    * Implemented `EmbeddedPermissionPromptObserver` to track the
      lifecycle and bounds of the embedded permission prompt widget. When
      it resizes, closes due to out of focus, or closes due to an option
      being selected, it sends a mojo message (`OnEmbeddedPermissionPromptChanged`)
    * Added a new Mojo method `OnEmbeddedPermissionPromptChanged`
      to tell the frontend when the permission prompt is visible,
      and the prompt's size
    * Made page callback passed down to `cr-composebox-voice-search`. Also
      made it protected instead of private.
    * Updated `cr-composebox-voice-search` to listen for permission state
        changes, effectively pausing the idle timer when the permission
        prompt is visible.

    screencast/cast/NTU0NDc5Mjc3MDQ3ODA4MHxiYzc3ZmYyYy1hNQ
    NO_IFTTT=just rearranged and made existing property protected
    It is known that it should be moved to mixin.

    Bug: b:492201887
    Change-Id: Ie85be91c7e2435bb519b7d5e92565674a1d5ffbf
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7744441
    Commit-Queue: James Leung <jamesleung@google.com>
    Reviewed-by: Ananya Seelam <ananyaseelam@google.com>
    Cr-Commit-Position: refs/heads/main@{#1631087}

* [149.0.7827.54] Filter upstream tests as needed.

* [149.0.7827.54] PrintViewManagerBase now needs settings passed into it.

Chromium change:
https://chromium.googlesource.com/chromium/src.git/+/fa1ec9c34a77a

commit fa1ec9c34a77aba67b0f7d9e36425149228c3a9a
Author: Lei Zhang <thestig@chromium.org>
Date:   Wed May 27 15:32:39 2026 -0700

    [M149] Print Preview: Remove PrintManagerHost.UpdatePrintSettings() dict param

    Original change's description:
    > Print Preview: Remove PrintManagerHost.UpdatePrintSettings() dict param
    >
    > In the Print Preview IPC dance, PrintPreviewHandler in the browser calls
    > PrintRenderFrame.PrintPreview() with a print settings dictionary.
    > PrintRenderFrameHelper, the PrintRenderFrame implementation,
    > conditionally makes a small edit to the dictionary, and passes it back
    > to PrintViewManagerBase in the browser in the
    > PrintManagerHost.UpdatePrintSettings() call.
    >
    > In modern Chromium, the browser process can make the same conditional
    > decision and modify the dictionary itself. As such, there is no need for
    > PrintRenderFrameHelper to pass it back. So simplify the
    > UpdatePrintSettings() Mojo interface to remove the dictionary parameter.
    > After this, rename it to GetPrintPreviewParams() since it is no longer
    > sending an update to the browser.
    >
    > On the browser side, pass the dictionary from PrintPreviewHandler to
    > PrintViewManagerBase, to compensate for the IPC change. The dictionary
    > needs to go into a queue as there may be multiple
    > PrintRenderFrame.PrintPreview() calls in quick succession.
    >
    > Update tests as needed to match the IPC changes. In several test cases,
    > calls TestPrintViewManager::CreateForWebContents() to properly install
    > the TestPrintViewManager, instead of allocating it on the stack.
    >
    > Bug: 513005991
    > Change-Id: Ie022900568c3bac7e086c9fbf9d6345a22e46278
    > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7866423
    > Reviewed-by: Andy Phan <andyphan@chromium.org>
    > Commit-Queue: Lei Zhang <thestig@chromium.org>
    > Reviewed-by: Tom Sepez <tsepez@chromium.org>
    > Cr-Commit-Position: refs/heads/main@{#1635224}

    (cherry picked from commit ea38e74cf233e5ae1e5c3cc7d02d3c36e025a754)

    Bug: 515954036,513005991

---------

Co-authored-by: Claudio DeSouza <cdesouza@brave.com>
2026-06-01 23:31:09 -04:00
..