Vaadin 14.1.2

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.
For the full release notes go to the GitHub releases.

Visit vaadin.com to get started.

Support

Vaadin 14 is an LTS (long term support) version, which will be supported for 5 years after the GA (general availability) release. More details of our release model are available on our roadmap page.

Vaadin also provides commercial support and warranty.

New and Noteworthy

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

Flow updates to 2.1.1

• Send sessionExpired as early as possible
• WebBrowser::isIPad method is deprecated
• Don't flush if flush underway
• Avoid shadow root access in TemplateInitializer
• Fix bug in Element::removeFromTree not removing virtual child nodes from their parent
• Accept a build-info
• Error message if dev-server not responding
• Don't use scroll position handler in embedded web components app
• Handle the error if the PWA icon is not loadable
• Prevent VaadinSession::setErrorHandler from accepting null
• Use the latest leaf bean instance from data provider
• Simplify Javadoc for @Route::absolute
• Update to the latest Testbench
• Do not add defer attribute to JS module element
• Improve InitialPageSettings::addInlineWithContents Javadoc
• Add "not null" Javadocs to a chain of text node methods
• Parse Polymer 2 template insertion style
• Remove all extra info from JSON file and make it easy to write for tests

Changes since 14.1.1

• Vaadin Flow (2.1.1)

Getting Started with Vaadin 14

App starters

The best way to get started with Vaadin 14 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. If you encounter an issue when using the HTML/JS API of a component or the component renders incorrectly, the problem is likely in the web component. The web component repositories are named like https://github.com/vaadin/vaadin-button
2. If you encounter an issue when using the Java API of a component, the problem is likely in the Flow integration of the web component. The Flow component integration repositories are named like https://github.com/vaadin/vaadin-button-flow
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