Skip to content

Upgrade from Chromium 149.0.7827.23 to Chromium 149.0.7827.48 (1.91.x) DO NOT MERGE#36852

Closed
mkarolin wants to merge 5 commits into
1.91.xfrom
149.0.7827.48-1.91.x
Closed

Upgrade from Chromium 149.0.7827.23 to Chromium 149.0.7827.48 (1.91.x) DO NOT MERGE#36852
mkarolin wants to merge 5 commits into
1.91.xfrom
149.0.7827.48-1.91.x

Conversation

@mkarolin

@mkarolin mkarolin commented May 29, 2026

Copy link
Copy Markdown
Collaborator

THIS IS ANDROID ONLY PR -- DO NOT MERGE

Resolves brave/brave-browser#55942

mkarolin and others added 4 commits May 29, 2026 16:28
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}
@mkarolin mkarolin self-assigned this May 29, 2026
@mkarolin mkarolin requested a review from a team as a code owner May 29, 2026 21:07
@mkarolin mkarolin added CI/skip-ios Do not run CI builds for iOS CI/run-network-audit Run network-audit CI/run-audit-deps Check for known npm/cargo vulnerabilities (audit_deps) CI/run-upstream-tests Run upstream unit and browser tests on Linux and Windows (otherwise only on Linux) CI/skip-windows-x64 Do not run CI builds for Windows x64 CI/skip-macos-arm64 Do not run CI builds for macOS arm64 labels May 29, 2026
@github-actions github-actions Bot added the CI/storybook-url Deploy storybook and provide a unique URL for each build label May 29, 2026
@mkarolin

mkarolin commented Jun 3, 2026

Copy link
Copy Markdown
Collaborator Author

Closing in favor of #36951

@mkarolin mkarolin closed this Jun 3, 2026
@mkarolin mkarolin deleted the 149.0.7827.48-1.91.x branch June 3, 2026 01:03
@mkarolin mkarolin added this to the Closed milestone Jun 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI/run-audit-deps Check for known npm/cargo vulnerabilities (audit_deps) CI/run-network-audit Run network-audit CI/run-upstream-tests Run upstream unit and browser tests on Linux and Windows (otherwise only on Linux) CI/skip-ios Do not run CI builds for iOS CI/skip-macos-arm64 Do not run CI builds for macOS arm64 CI/skip-windows-x64 Do not run CI builds for Windows x64 CI/storybook-url Deploy storybook and provide a unique URL for each build

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants