Vaadin 19.0.8

Vaadin consists of a set of web components, a Java web framework, configurable themes, tools and a set of app templates.

This is a maintenance release of Vaadin.
See the full release notes for vaadin 19.0 in GitHub releases, including new features, getting started, supported browsers and other technologies, and migration notes.

Visit vaadin.com to get started.

New and Noteworthy

Here are the highlighted new and improved features in this maintenance release.

Vaadin Flow (6.0.9)

Changes in Flow from 6.0.8

• Fixes:

  • ⧉ Use regular string enum instead of a const enum (#10853). PR:10860
    Given a Java enum as

    pubic enum Environment {
      DEV, TEST, PROD
    }

    Now it is possible to do any object action with the final Environment enum on the client-side:

    Object.keys(Environment).forEach(enumValue => console.log(enumValue));

  • ⧉ Remove old router layouts content before navigation (#10973). PR:11008. Ticket:345

    Recursively removes content of the all nested router layouts of the given old content when the navigation occurs. This is needed to let Dependency Injection frameworks (Spring and CDI add-ons) to re-create managed components with no duplicates/leftovers.

  • ⧉ Change construct-style-sheets-polyfill to be a runtime dependency (#10991). PR:10995. Ticket:10988

  • ⧉ Update the used Opcode from 7 to 8 (#10979). PR:10983. Ticket:10870

    Update used ClassVisitor ASM version from 7 to 8 to support Java16 record

  • ⧉ Use IOUtils toStream and toString (#10975). PR:10977. Ticket:10893

    Use IOUtils toString and toInputStream to not change any characters in the file content.

  • ⧉ Enable use of external css using @import (#10953). PR:10962. Ticket:10228

    Add fix for using a external css file by having the @import url(...) in a css file. Also supports imports with media queries.

  • ⧉ Use defined version for devDependencies. (#10955). PR:10959

  • ⧉ Allow empty segments at start (#10921). PR:10936. Ticket:10729

  • ⧉ Log limitation of adding new styles while switching themes (#10894). PR:10928. Ticket:10680

    If there are more than one theme available in themes folder, user can switch between them in development mode by changing the name of the theme in @theme. As having a watch for adding new styles in component folder is 'static', at least a log about this limitation is needed.

Components

Changes in Vaadin-Select-Flow

• Fixes:
  • ⧉ disable client side validation PR:986. Ticket:265

webcomponent versions listed in this release 19.0.8

• Vaadin Accordion (web component v1.2.0)
• Vaadin App Layout (web component v2.2.0)
• Vaadin Avatar (web component v2.0.2)
• Vaadin Button (web component v2.4.0)
• Vaadin Checkbox (web component v3.0.0)
  • Checkbox
  • Checkbox Group
• Vaadin Combo Box (web component v6.0.1)
• Vaadin Context Menu (web component v5.0.0)
• Vaadin Custom Field (web component v2.0.0)
• Vaadin Date Picker (web component v5.0.0)
• Vaadin Date Time Picker (web component v2.0.0)
• Vaadin Details (web component v1.2.0)
• Vaadin Dialog (web component v2.5.2)
• Vaadin Form Layout (web component v2.3.0)
• Vaadin Grid (web component v6.0.2)
  • Grid
  • Tree Grid
  • Grid Context Menu
• Vaadin Icons (web component v4.3.2)
• Vaadin List Box (web component v2.0.0)
• Vaadin Login (web component v2.0.0)
• Vaadin Menu Bar (web component v2.0.0)
• Vaadin Notification (web component v1.6.1)
• Vaadin Ordered Layout (web component v1.4.0)
  • Horizontal Layout
  • Vertical Layout
  • Flex Layout
• Vaadin Progress Bar (web component v1.3.0)
• Vaadin Radio Button (web component v1.5.1)
  • Radio Button
  • Radio Button Group
• Vaadin Select (web component v3.0.0)
• Vaadin Split Layout (web component v4.3.0)
• Vaadin Tabs (web component v4.0.0)
• Vaadin Text Field (web component v3.0.2)
  • Text Field
  • Text Area
  • Password Field
  • Big Decimal Field
  • Email Field
  • Integer Field
  • Number Field
• Vaadin Time Picker (web component v3.0.0)
• Vaadin Upload (web component v5.0.0)
• Vaadin Board (PRO) (web component v3.0.0)
• Vaadin Charts (PRO) (web component v8.0.2)
• Vaadin Confirm Dialog (PRO) (web component v2.0.0)
• Vaadin Cookie Consent (PRO) (web component v2.0.0)
• Vaadin Crud (PRO) (web component v2.0.1)
• Vaadin Grid Pro (PRO) (web component v3.0.1)
• Vaadin Rich Text Editor (PRO) (web component v2.0.0)

Support

vaadin 19 is supported for one month after Vaadin 20 has been released. The latest LTS (long term support) version is Vaadin 14. More details of our release model are available on our roadmap page.

Vaadin also provides commercial support and warranty.

Getting Started with Vaadin

App starters

The best way to get started with Vaadin is to go to https://start.vaadin.com and configure your new application by setting up your views, entities, styles, and the technology stack you’re interested in.

For the full list of how to get started go to the GitHub releases.

Known Issues and Limitations

Flow

Components

Reporting Issues

We appreciate if you try to find the most relevant repository to report the issue in. If it is not obvious which project to add issues to, you are always welcome to report any issue at https://github.com/vaadin/platform/issues.

A few rules of thumb will help you and us in finding the correct repository for the issue:

1. Bug tickets and enhancement requests that are specific to a certain Vaadin component should be posted in the component's Web Component repostory (e.g. https://github.com/vaadin/vaadin-button for Button).
2. Issues that are not component-specific (e.g. requests for new components) or encompass multiple components should be posted in vaadin-flow-components repository.
3. If you encounter an issue with Flow which does not seem to be related to a specific component, the problem is likely in Flow itself. The Flow repository is https://github.com/vaadin/flow
4. If you encounter an issue with Designer, the repository is https://github.com/vaadin/designer
5. If you encounter an issue with TestBench, the repository is https://github.com/vaadin/testbench