syncfusion-blazor-toolkit-popups

Use SfDialog when you need to block the UI for required input or confirmation, and SfTooltip for brief informational text on hover or focus. The decision matrix compares lifecycle, ARIA semantics, focus trapping, and trigger modes side by side.

Bind visibility with @bind-Visible, set IsModal="true" and ShowCloseIcon="true", then declare DialogButtons with individual OnClick handlers. Use the cancelable OnClose event with args.Cancel = true to prevent closing when there are unsaved changes.

Disabled buttons do not fire mouse or focus events, so SfTooltip never triggers. Wrap the disabled SfButton in a focusable span with tabindex="0", or render the explanation as visible fallback text next to the control.

SfTooltip supports Auto (hover or focus, the default), Hover, Focus, Click, and Custom for programmatic Show/Hide control. Use Auto for buttons and links, and reserve Click for non-interactive triggers like spans or paragraphs.

Yes, place an EditForm with a model and OnValidSubmit handler inside DialogTemplates content, and trigger saving from a button inside the form. Set AllowPrerender="false" when the dialog body depends on interactive content or JS interop.

Never use SfTooltip for confirmations because it cannot block the page, traps no focus, and dismisses on Escape or blur. Use SfDialog with IsModal="true" so the user must explicitly accept or cancel before proceeding.