SmartCard: Don't use stronger terminology for block button
Context: go/web-smart-card-api-permissions
Clicking the block button on permission prompt for smart card readers
by design doesn't have "never allow" behaviour. Hence, the stronger
terminology does not apply in this case.
Bug: 40275778
Change-Id: I4acb7b8cddb1985c49a89c4c660082b58c791f98
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6337763
Commit-Queue: Luke Klimek <[email protected]>
Reviewed-by: Simon Hangl <[email protected]>
Reviewed-by: Dominik Bylica <[email protected]>
Reviewed-by: Balazs Engedy <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1432361}
diff --git a/components/permissions/permission_request.h b/components/permissions/permission_request.h
index 6709e5a..935c7303 100644
--- a/components/permissions/permission_request.h
+++ b/components/permissions/permission_request.h
@@ -147,6 +147,13 @@
// The default implementation returns std::nullopt (ie, use generic text).
virtual std::optional<std::u16string> GetAllowAlwaysText() const;
+ // Returns the text to be used in the "block" button of the permission
+ // prompt.
+ //
+ // If not provided, the generic text for this button will be used instead.
+ // The default implementation returns std::nullopt (ie, use generic text).
+ virtual std::optional<std::u16string> GetBlockText() const;
+
// Whether the request was initiated by the user clicking on the permission
// element.
bool IsEmbeddedPermissionElementInitiated() const;
