Popconfirm

Demos

How to import

<script lang="ts">
    import { Popconfirm } from '@fibrae/semi-ui-svelte';
</script>

Basic Usage

Popconfirm is based on the Tooltip component. Children support the same type as Tooltip. For details, please refer to Tooltip Cautions

<script lang="ts">
    import { Button, Popconfirm, Toast } from '@fibrae/semi-ui-svelte';

    const onConfirm = () => {
        Toast.success('确认保存！');
    };

    const onCancel = () => {
        Toast.warning('取消保存！');
    };
</script>

<Popconfirm {onCancel} {onConfirm} title="确定是否要保存此修改？">
    <Button>保存</Button>
    {#snippet content()}此修改将不可逆{/snippet}
</Popconfirm>

Type collocation

Developers can use scenario-based okType/cancelType and the icon snippet to match different styles of bubble confirmation boxes. Without icon the default warning icon is shown; icon={null} renders no icon.

<script lang="ts">
    import { IconAlertTriangle } from '@fibrae/semi-icons-svelte';
    import { Button, Popconfirm, Radio, RadioGroup, type RadioValue } from '@fibrae/semi-ui-svelte';

    type TypeKey = 'default' | 'warning' | 'danger' | 'tertiary';

    const typeMap: Record<TypeKey, { okType?: 'danger'; color?: string }> = {
        default: {},
        warning: { color: 'var(--semi-color-warning)' },
        danger: { okType: 'danger', color: 'var(--semi-color-danger)' },
        tertiary: { color: 'var(--semi-color-tertiary)' },
    };
    const keys = Object.keys(typeMap) as TypeKey[];
    let value = $state<RadioValue | undefined>('default');
    let visible = $state(true);
    const type = $derived(keys.find((key) => key === value) ?? 'default');
</script>

<div>
    <RadioGroup bind:value style="margin-top: 14px; margin-bottom: 14px" type="button">
        {#each keys as key (key)}
            <Radio value={key}>
                <span style={`color: var(--semi-color-${key === 'default' ? 'primary' : key})`}>{key}</span>
            </Radio>
        {/each}
    </RadioGroup>
    <div>
        <Popconfirm bind:visible okType={typeMap[type].okType} title="确定是否要保存此修改？" trigger="custom">
            <Button onclick={() => (visible = !visible)}>点击此处</Button>
            {#snippet icon()}
                <IconAlertTriangle size="extra-large" style={typeMap[type].color ? `color: ${typeMap[type].color}` : undefined} />
            {/snippet}
            {#snippet content()}此修改将不可逆{/snippet}
        </Popconfirm>
    </div>
</div>

Delay hide

onConfirm and onCancel can be closed after click through return Promise.
When onCancel and onConfirm are triggered, the corresponding Button will automatically switch to loading: true
promise solve will close the bubble confirmation box, the bubble will remain when promise reject, and button loading will automatically switch to false

<script lang="ts">
    import { Button, Popconfirm } from '@fibrae/semi-ui-svelte';

    const onConfirm = () =>
        new Promise<void>((resolve) => {
            setTimeout(() => {
                console.log('resolve,close popconfirm');
                resolve();
            }, 2000);
        });

    const onCancel = () =>
        new Promise<void>((_resolve, reject) => {
            setTimeout(() => {
                console.log('reject, popconfirm still exist');
                reject();
            }, 2000);
        });
</script>

<Popconfirm {onCancel} {onConfirm} title="确定是否要保存此修改？">
    <Button>保存</Button>
    {#snippet content()}此修改将不可逆{/snippet}
</Popconfirm>

Initialize the Focus Position of Popup Layer

okButtonProps and cancelButtonProps support passing in the autoFocus parameter, which will automatically focus at this position when the panel is opened.

The content snippet receives { initialFocusRef } as its argument. Bind it to the focusable DOM or component with {@attach initialFocusRef}, and it will automatically focus at this position when the panel is opened. When a button autoFocus and initialFocusRef are both given, the button wins.

<script lang="ts">
    import { Button, Popconfirm, Space } from '@fibrae/semi-ui-svelte';
</script>

{#snippet text()}此修改将不可逆{/snippet}

<Space>
    <Popconfirm content={text} okButtonProps={{ autoFocus: true, type: 'danger' }} title="确定是否要保存此修改？">
        <Button>确认聚焦</Button>
    </Popconfirm>
    <Popconfirm cancelButtonProps={{ autoFocus: true }} content={text} title="确定是否要保存此修改？">
        <Button>取消聚焦</Button>
    </Popconfirm>
    <Popconfirm title="确定是否要保存此修改？">
        <Button>内容聚焦</Button>
        {#snippet content({ initialFocusRef })}
            <input {@attach initialFocusRef} placeholder="focus here" />
        {/snippet}
    </Popconfirm>
</Space>

Use with Tooltip or Popover

Please refer to Use with Tooltip/Popover

API Reference

Props

Methods

class and style land on the confirmation card, and the props in okButtonProps and cancelButtonProps land on their buttons (except autoFocus); bind:this receives the focusTrigger handle. Popconfirm has no root DOM element, so other undeclared native attributes and events are dropped.

Accessibility

ARIA

• Whatever the trigger, hover and focus included, the Popconfirm popup has role dialog, named by title (by content when there is no title); the role prop overrides it
• For the rest, please refer to Popover

Keyboard and focus

• Popconfirm must have trigger, trigger can be focused, use Enter key to open Popconfirm
• After Popconfirm is activated, press the arrow key ⬇️ to move the focus to Popconfirm. The initial focus of Popconfirm should follow several principles:
  • If the Popconfirm contains the last step of an irreversible process, such as: deleting data, etc., then this initial focus is preferably on the least destructive interactable element, such as: the cancel button (by passing the autoFocus to the object cancelButtonProps)
  • If you only read text in Popconfirm, it is recommended to set the initial focus on the most likely interactive elements, such as: confirm button (implemented by passing autoFocus to the object okButtonProps )
• Keyboard users can dismiss Popconfirm by pressing Esc and focus should return to the trigger. After the user closes the Pop through the interactive element within the Popconfirm, the focus should also return to the trigger (except when trigger is custom)
• When it is opened, after the user clicks Esc in the blank space in Popconfirm, the focus will also return to the trigger (except when trigger is custom)

Design Tokens

FAQ

• Why does the Popconfirm floating layer lose its width and wrap unexpectedly when the width is not enough near the screen border?

  After Chromium 104, the wrapping rendering strategy when the width of the screen border text is not enough has changed. For details, see issue #1022, the semi-side has been This problem was fixed in v2.17.0.