Add prop(s) to hide popconfirm actions
See original GitHub issueThis function solves the problem (这个功能解决的问题)
More consistency between Popconfirms and Popovers
Expected API (期望的 API)
<template>
<n-popover>
<template #trigger>
<n-button> Hover </n-button>
</template>
<!-- NOTE because popovers can have a header, perhaps there should be a separate header icon slot -->
<template #header-icon>
<n-icon><!-- selected icon --></n-icon>
</template>
<template #icon>
<n-icon><!-- selected icon --></n-icon>
</template>
<!-- popover text -->
</n-popover>
</template>
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Add prop(s) to hide popconfirm actions · Issue #770 - GitHub
This function solves the problem (这个功能解决的问题) More consistency between Popconfirms and Popovers Expected API (期望的 API) Hover.
Read more >How to add popconfirm from antd design to file removal action
I want to show PopConfirm each time the user is trying to remove uploaded file. But the problem is: PopConfirm require React Element...
Read more >antd Popconfirm TypeScript Examples - ProgramCreek.com
The following examples show how to use antd.Popconfirm. You can vote up the ones you like or vote down the ones you don't...
Read more >ReactJS UI Ant Design Popconfirm Component - GeeksforGeeks
Popconfirm is a simple and compact confirmation dialog of an action. It is basically used to ask for user confirmation.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Actually they are nearly the same, popconfirm just wrap popover with some extra DOM.
It’s possible to make it like
However I won’t do that. It won’t make user’s DX better but add a lot of work in library development.
Yes I think you can do it.