Restore ClipboardButton
to work in non-secure contexts. (6.0
)
#19665
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: This is a backport of #19654 to
6.0
.Description
Motivation and Context
This PR is restoring ClipboardButton's functionality to work in non-secure context. In a previous refactoring (#17472), the component was made to use CopyButton from Mantine, which works only in secure contexts (+ localhost), unfortunately. This PR is now restoring it by removing the usage of Mantine's CopyButton and implements an own component for this, which uses our own copyToClipboard abstraction, which falls back to a legacy approach in non-secure contexts.
Fixes #19643.
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: