Vaadin 14.0.13
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.
Vaadin Flow 2.0.18
- Give hint about missing null representation in error message
- Include
flow-server-production-modeintoflow-bom - Remove removed binding from
changedBindingfield - Fix uber
jarbuild file finding - Prevent
npm --versionfrom querying the internets for updates - Handle client-initiated resync request
- Add
HasErrorParameterclasses to the endpoints
Vaadin Multiplatform Runtime
- Automatic redeployment (hot swap) causes an exception on MprServlet
- MPR Version checking potentially clashes with other libraries
- "This UI instance is already initialized" appearing in production
Components
-
Vaadin Combo Box (
js component)- do not use array in querySelector
- update event listener registrations
-
Vaadin Date Picker & Vaadin Time Picker & Vaadin Text Field (
java component)- fix server side validation:
- Note:
- is only done on the server side using the validation constraints of the component.
- is done on value change and not on blurring the field.
- has lesser priority than
Bindervalidation in case it is used.
- Note:
- fix server side validation:
-
Vaadin Grid
- Fixed issue with IOS13 iPad detection
-
Vaadin Board & Vaadin Charts
- only run license checker when needed
Changes since 14.0.12
- Vaadin Flow (2.0.18)
- Vaadin Multiplatform Runtime (Prime) for Framework 7 (2.0.1)
- Vaadin Multiplatform Runtime (Prime) for Framework 8 (2.0.1)
- Vaadin Combo Box (Flow integration 3.0.6, web component v5.0.9)
- Vaadin Date Picker (Flow integration 2.0.5, web component v4.0.5)
- Vaadin Time Picker (Flow integration 2.0.3, web component v2.0.4)
- Vaadin Grid (Flow integration 4.0.11, web component v5.4.12)
- Grid
- Tree Grid
- Grid Context Menu
- Vaadin Text Field (Flow integration 2.0.8, web component v2.4.14)
- Text Field
- Text Area
- Password Field
- Email Field
- Number Field
- Vaadin Board (PRO) (Flow integration 3.0.1, web component v2.1.1)
- Vaadin Charts (PRO) (Flow integration 7.0.2, web component v6.2.4)
- Vaadin Confirm Dialog (PRO) (Flow integration 2.0.2, web component v1.1.5)
- Vaadin Cookie Consent (PRO) (Flow integration 2.0.2, web component v1.1.2)
- Vaadin Grid Pro (PRO) (Flow integration 2.0.3, web component v2.0.5)
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.
Known Issues and Limitations
OSGi support
- OSGi with npm does not work in V14.0.0. We are working on a fix for V14.x.
- OSGi with Bower has problems with V14.0.0 but we are working on a fix to be released in a maintenance version (V14.0.X)
Flow
- The Template-in-Template feature has some limitations
- There are some issues in using Web Sockets as the Push channel in certain OSGi environments, but long polling works.
Components
- The dark theme preset does not work in IE11 when applied to the
<html>element.
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:
- 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
- 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
- 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
- If you encounter an issue with Designer, the repository is https://github.com/vaadin/designer
- If you encounter an issue with TestBench, the repository is https://github.com/vaadin/testbench