-
Notifications
You must be signed in to change notification settings - Fork 748
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Confirm: ability to adjust button label and class of global confirmation #11929
Comments
What would also be nice here is: <p:confirm header="Confirm delete">
<p>Are you sure to delete?</p>
... some formatted content here instead of a single line ...
</p:confirm> |
This comment has been minimized.
This comment has been minimized.
@fcorneli the Confirm is a Behavior and I don't think Behaviors can have children or facets like you have posted? I could be wrong? |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
@melloware @BalusC What do you think of an additional |
@mkomko i don't see why not. I will add these two new fields. |
Description
It would be nice to be able to adjust button labels and classes of a global confirm dialog via
<p:confirm>
. It's currently already possible to adjust the header and message of a global confirm dialog but nothing else than that.Describe the solution you would like
Imaginary code:
yesButtonLabel
: overrides label of 'Yes' button (and restores it before the global confirm dialog is reused elsewhere)yesButtonClass
: adds given class to 'Yes' button (and removes it before the global confirm dialog is reused elsewhere)noButtonLabel
: overrides label of 'No' button (and restores it before the global confirm dialog is reused elsewhere)noButtonClass
: adds given class to 'No' button (and removes it before the global confirm dialog is reused elsewhere)Additional context
Currently I'm working around this with a patched
PrimeFaces.widget.ConfirmDialog
which inspects a customtype
inshowMessage()
function.The text was updated successfully, but these errors were encountered: