-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
New ConfirmDialog Component #901
Comments
I want some more functionality in dialog like button label text because I have more confirmation dialog in a a single template. |
What I think could fit nicely is allow html messages. Instead of
We do
What do you think, @cagataycivici ? |
@KumarGovindh Did you find how to customize acceptLabel and rejectLabel? |
Hi again, I found how to do it, you just have to defined in you p-confirmDialog acceptLabel=""; for example:
|
Why cant we simply pass the confirmdialog template to the service? |
@barocsi Take a look at p-dialog. |
Thanks, but this is not the way it should work. Why would I pollute my static dom with dialogs instead of having generic templates that I can display dynamically? It smells like an anti-pattern. |
Has anyone found the proper solution ? |
Any news about this feature? Should we open an issue for creating more confirmDialog on the same page? |
Does the p-confirmDialog support a ng-template pTemplate="body" ? |
the solution for my is appendTo="body" <p-confirmDialog header="Confirmation" icon="fa fa-question-circle" width="425" appendTo="body" #cd> |
Did you have any possible in multi line of content in confirmation box ? |
Is there no way to close these confirmation dialogs using the service? I want to display a "Your session is going to expire" message, and close the confirmation if the session expires—but there doesn't appear to be a way to do that. |
@shaungrady use normal dialog with modal=true |
Subset of Dialog to make it easier to create a confirm dialog with backed by a confirm service for reuse so could be fired from any action.
The text was updated successfully, but these errors were encountered: