Files
brave-core/browser/ai_chat
Claudio DeSouza 40c3d6b3dd [cr149] ContentSettingPermissionResolver dropped from request data
This changes the constructor calls, and this change corrects that. For
the only use of `PermissionDescriptor` in the constructor, a default
constructor is being used because there is no blink value for the
permission name for `RequestType::kBraveOpenAIChat`, so we set that
separately.

Chromium changes:
https://chromium.googlesource.com/chromium/src/+/35ad82c9803604df82915104d4d062cd851214f7

commit 35ad82c9803604df82915104d4d062cd851214f7
Author: Antonio Sartori <antoniosartori@chromium.org>
Date:   Thu Apr 23 10:37:35 2026 -0700

    [permissions] Refactor PermissionRequestData

    This CL refactors PermissionRequestData so that it becomes again a
    data-only struct (which can be e.g. cloned) by removing the
    PermissionResolver member. This allows simplifying
    GeolocationPermissionContextAndroid, where we don't need to recreate
    fake PermissionRequestData for the callbacks anymore.

    The refactoring unfortunately implies adapting all callsites, which
    however become more natural as they don't need to instantiate a
    PermissionResolver anymore.

    R=hempjudith@google.com

    Change-Id: Ib7883e9f7cac32ef4039ce3098275ad9018f47d3
    Bug: 443898320
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7780845
    Commit-Queue: Antonio Sartori <antoniosartori@chromium.org>
    Reviewed-by: Javier Fernandez <jfernandez@igalia.com>
    Reviewed-by: Judith Hemp <hempjudith@google.com>
    Reviewed-by: Marc Treib <treib@chromium.org>
    Cr-Commit-Position: refs/heads/main@{#1619624}
2026-05-22 16:25:11 -04:00
..
2026-05-22 16:25:09 -04:00
2026-05-22 16:18:03 -04:00