Zum Hauptinhalt springen Seitenleiste
Zum Inhaltsverzeichnis springen

    Dialog

    <pc-dialog> 0.5.1 experimental

    Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.

    Dialogs, sometimes called “modals”, appear above the page and draw the user’s immediate attention.

    <pc-dialog label="Dialog" class="dialog-overview">
        Lorem ipsum dolor sit amet, consectetur adipiscing elit.
    
        <pc-button variant="plain" slot="footer" data-dialog="close">
            Close
        </pc-button>
    </pc-dialog>
    
    <pc-button>Open dialog</pc-button>
    
    <script>
        const dialog = document.querySelector(".dialog-overview");
        const openButton = dialog.nextElementSibling;
    
        openButton.addEventListener("click", () => (dialog.open = true));
    </script>
    Code Edit

    Demos#

    Opening and closing dialogs declaratively#

    You can open and close dialogs with JavaScript by toggling the open attribute, but you can also do it declaratively. Add the data-dialog="open id" to any button on the page, where id is the id of the dialog you want to open.

    Edit

    Similarly, you can add data-dialog="close" to a button inside of the dialog to tell it to close it.

    Edit

    Custom width#

    Use the --width custom property to set the dialog’s width.

    Edit

    Scrolling#

    By design, a dialog’s height will never exceed that of the viewport. As such, dialogs will not scroll with the page ensuring the header and footer are always accessible to the user.

    Edit

    Header actions#

    The header shows a functional close button by default. You can use the header-actions slot to add additional icon buttons if needed.

    Edit

    Prevent light dismissal#

    If you want to prevent the dialog from closing if the user clicks on the overlay, add the no-light-dismiss attribute.

    Edit

    Prevent dialog from closing#

    By default, dialogs will close when the user clicks the close button, clicks the overlay or presses the Esc key. In most cases, the default behaviour is the best behaviour in terms of UX. However, there are situations where this may be undesirable, such as when data loss will occur.

    To keep the dialog open in such cases, you can cancel the pc-hide event. When cancelled, the dialog will remain open and pulse briefly to draw the user’s attention to it.

    You can use event.detail.source to check what triggered the close request. In this example, the dialog will only close when a custom close button inside the footer is clicked. Clicking the overlay, pressing Esc or using the built‐in header close button will all be prevented.

    Edit

    Customise initial focus#

    By default, the dialog’s panel will gain focus when opened. This allows a subsequent tab press to focus on the first tabbable element in the dialog. If you want a different element to have focus, add the autofocus attribute to it as shown below.

    Edit

    Eigenschaften#

    NameBeschreibungReflektiertStandard
    openIndicates whether or not the dialog is open. Toggle this attribute to show and hide the dialog.
    Typ: boolean
    false
    labelThe dialog’s label displayed in the header. You should always include a relevant label even when using the no-header attribute, as it is required for proper accessibility. If you need to display HTML, use the label slot instead.
    Typ: string
    ""
    noHeader
    no-header
    Removes the header. This will also remove the default close button, so please ensure you provide an easy, accessible way for users to dismiss the dialog.
    Typ: boolean
    false
    noLightDismiss
    no-light-dismiss
    Prevents clicks on the backdrop causing the dialog to close.
    Typ: boolean
    false
    updateComplete Ein schreibgeschütztes Promise, das erfüllt ist, sobald die Komponente fertig aktualisiert wurde.

    Erfahre mehr über Attribute und Eigenschaften.

    Slots#

    NameBeschreibung
    (default)The dialog’s main content.
    labelThe dialog’s label. Alternatively, you can use the label attribute.
    header-actionsOptional actions to add to the header. Works best with <pc-button>.
    footerThe dialog’s footer, usually one or more buttons representing various options.

    Erfahre mehr über die Benutzung von Slots.

    Events#

    NameBeschreibungEvent‐Detail
    pc-showEmitted when the dialog opens.
    pc-after-showEmitted after the dialog opens and all animations are complete.
    pc-hideEmitted when the dialog closes.{ source: Element }
    pc-after-hideEmitted after the dialog closes and all animations are complete.

    Erfahre mehr über Events.

    Benutzerdefinierte Eigenschaften#

    NameBeschreibungStandard
    --widthThe preferred width of the dialog. Note that the dialog will shrink to accommodate smaller screens.31rem
    --header-spacingThe amount of spacing to use for the header.var(--pc-spacing-xl)
    --body-spacingThe amount of padding to use for the body.var(--pc-spacing-s) var(--pc-spacing-xl)
    --footer-spacingThe amount of padding to use for the footer.var(--pc-spacing-s) var(--pc-spacing-xl) var(--pc-spacing-xl)

    Erfahre mehr über das Anpassen von benutzerdefinierten Eigenschaften.

    Parts#

    NameBeschreibung
    dialogThe dialog’s <dialog> element.
    headerThe dialog’s header. This element wraps the title and header actions.
    header-actionsOptional actions to add to the header. Works best with <pc-button>.
    titleThe dialog’s title.
    close-buttonThe close button. Is a <pc-button> under the hood.
    close-button-baseThe close button’s base part.
    bodyThe dialog’s body.
    footerThe dialog’s footer.

    Erfahre mehr über das Anpassen von CSS‐Parts.

    Animationen#

    NameBeschreibung
    dialog.showThe animation to use when showing the dialog.
    dialog.hideThe animation to use when hiding the dialog.
    dialog.denyCloseThe animation to use when a request to close the dialog is denied.

    Erfahre mehr über das Anpassen von Animationen.

    Importieren#

    Wenn du den Autoloader oder den Standard‐Loader nutzt, kannst du diesen Abschnitt überspringen. Falls du „Cherry Picking“ betreibst, kannst du die folgenden Snippets verwenden, um diese Komponente zu importieren.

    CDN (Skript‐Tag)CDN (Import)npm (Import)

    Um diese Komponente manuell vom CDN zu importieren, kopiere dieses Code‐Snippet und füge es in dein HTML ein.

    <script type="module" src="https://cdn.jsdelivr.net/npm/placer-toolkit@1.0.0-alpha.3/cdn/components/dialog/dialog.js"></script>

    Um diese Komponente manuell vom CDN zu importieren, kopiere dieses Code‐Snippet und füge es in deine JavaScript‐Datei ein.

    import "https://cdn.jsdelivr.net/npm/placer-toolkit@1.0.0-alpha.3/cdn/components/dialog/dialog.js";

    Um diese Komponente manuell via npm zu importieren, kopiere dieses Code‐Snippet und füge es in deine JavaScript‐Datei ein.

    import "placer-toolkit/dist/components/dialog/dialog.js";

    Abhängigkeiten#

    Diese Komponente importiert automatisch folgende Komponenten:

    Wir würden uns freuen, von dir zu hören. Bitte kontaktiere uns bei Fragen oder Anliegen, die du hast.

    Du kannst uns per E‐Mail unter placer.coc.reports+contact@gmail.com erreichen.

    Wir freuen uns darauf, von dir zu hören!

    Alles klar!
    Gefährliche Lande

    Ui! Du bist in die gefährlichen Lande von Placer Toolkit geraten. Version 0 ist veraltet und entspricht nicht den EU‐Datenschutzstandards, einschließlich DSGVO.

    Willst du die neuesten Kräfte, Sicherheit und Compliance? Bleib bei der aktuellen Version von Placer Toolkit!

    Ups! Aufladen!