You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation for nzOkType says "Button type of the OK button. Consistent with the type of the nz-button."
The button types in nz-button are primary, default, dashed, text, and link. To get a danger nz-button you should use the attribute nzDanger, so I expect to set something like
I have to use nzOkType="danger" or type: "danger" as there is no property for nzOkDanger or configuration item for danger (There is a configuration item for ghost in nzFooter/ModalButtonOptions though)
This gives me primary danger buttons using the old class ant-btn-danger instead of the new ant-btn-primary ant-btn-dangerous
Environment
Info
ng-zorro-antd
10.1.2
Browser
Any
The text was updated successfully, but these errors were encountered:
Hello @oestrogen. We totally like your proposal/feedback, welcome to send us a Pull Request for it. Please fill the Pull Request Template here, provide documentation/test cases if needed and make sure CI passed, we will review it soon. Appreciate it advance and we are looking forward to your contribution!
Reproduction link
https://stackblitz.com/edit/angular-nimze4?file=src/app/app.component.ts
Steps to reproduce
Create a modal with a danger button
What is expected?
The documentation for nzOkType says "Button type of the OK button. Consistent with the type of the nz-button."
The button types in nz-button are primary, default, dashed, text, and link. To get a danger nz-button you should use the attribute nzDanger, so I expect to set something like
For nzFooter I expect something like
What is actually happening?
I have to use
nzOkType="danger"
ortype: "danger"
as there is no property fornzOkDanger
or configuration item fordanger
(There is a configuration item forghost
in nzFooter/ModalButtonOptions though)This gives me primary danger buttons using the old class
ant-btn-danger
instead of the newant-btn-primary ant-btn-dangerous
The text was updated successfully, but these errors were encountered: