Vaadin 18.0.7

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 18.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.

Changes in Flow from 5.0.3

• Fixes:

  • ⧉ Options in the Combo Box's selection list are consistent and not disappearing when first searching and then selecting them. This was happening while using Combo Box with a ComponentRenderer. (#9783). PR:10054. Ticket: vaadin/flow-components#437

  • ⧉ Resolve requested range properly after filtering the lazy backend (#10020). PR:10028. Ticket:9988

• Behaviour changes:

  • ⧉ Element::removeAllChildren behaviour has been changed (#10128) so that the re-attached node persists its state "removed children" between client-server roundtrips. It wasn't a case before that change, the "clear all" event happens only once after first attach of the node.
    That effectively means that if you have a client-side LitElement component and corresponding LitTemplate java-side component, then once you call Element::removeAllChildren on java-side, it will remove all children on client-side on every attach action. Ticket:10119

Components

• vaadin-grid
  • Warranty fix : fix: Flush debounceIncreasePool on loadPage if scrolling (ticket)
  • fix: make explicit data request when clearing cache with no initial pool

Support

Vaadin 18 is supported for one month after Vaadin 19 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://vaadin.com/start and pick an app template for the technology stack you’re interested in.

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

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