@vaadin/vaadin-dialog

<vaadin-dialog>

Live Demo ↗ | API documentation ↗

<vaadin-dialog> is a Web Component for customized modal dialogs, part of the Vaadin components.

<vaadin-dialog opened>
  <template>
    Sample dialog
  </template>
</vaadin-dialog>

Installation

The Vaadin components are distributed as Bower and npm packages. Please note that the version range is the same, as the API has not changed. You should not mix Bower and npm versions in the same application, though.

Unlike the official Polymer Elements, the converted Polymer 3 compatible Vaadin components are only published on npm, not pushed to GitHub repositories.

Polymer 2 and HTML Imports Compatible Version

Install vaadin-dialog:

bower i vaadin/vaadin-dialog --save

Once installed, import it in your application:

<link rel="import" href="bower_components/vaadin-dialog/vaadin-dialog.html">

Polymer 3 and ES Modules Compatible Version

Install vaadin-dialog:

npm i @vaadin/vaadin-dialog --save

Once installed, import it in your application:

import '@vaadin/vaadin-dialog/vaadin-dialog.js';

Getting Started

Vaadin components use the Lumo theme by default.

The file structure for Vaadin components

• src/vaadin-dialog.html

  Unstyled component.

• theme/lumo/vaadin-dialog.html

  Component with Lumo theme.

• vaadin-dialog.html

  Alias for theme/lumo/vaadin-dialog.html

Running demos and tests in browser

1. Fork the vaadin-dialog repository and clone it locally.

2. Make sure you have npm installed.

3. When in the vaadin-dialog directory, run npm install and then bower install to install dependencies.

4. Run polymer serve --open, browser will automatically open the component API documentation.

5. You can also open demo or in-browser tests by adding demo or test to the URL, for example:

• http://127.0.0.1:8080/components/vaadin-dialog/demo
• http://127.0.0.1:8080/components/vaadin-dialog/test

Running tests from the command line

1. When in the vaadin-dialog directory, run polymer test

Following the coding style

We are using ESLint for linting JavaScript code. You can check if your code is following our standards by running gulp lint, which will automatically lint all .js files as well as JavaScript snippets inside .html files.

Contributing

• Make sure your code is compliant with our code linters: gulp lint
• Check that tests are passing: polymer test
• Submit a pull request with detailed title and description
• Wait for response from one of Vaadin components team members

License

Apache License 2.0

Vaadin collects development time usage statistics to improve this product. For details and to opt-out, see https://github.com/vaadin/vaadin-usage-statistics.