Vaadin 14.1.17
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 14.1 in GitHub releases, including new features, getting started, supported browsers and other technologies, and migration notes.
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.
Note: Vaadin 14.1.17 bumps from Flow 2.1.3 to 2.1.5.
Vaadin Flow 2.1.5 is a maintenance release for Vaadin 14.1 with the following changes:
Warranty Fixes:
- Confirmed duplicate message from the client if a Throwable is thrown
- Grid with Custom Components based on PolymerTemplate throw NPE
- No message when cookies are disabled
- UI freezes randomly with client error
- BeforeLeaveObserver.beforeLeave() not invoked on Page.setLocation() documentation
- Issue with UI refresh from async thread
Bugfixes
- Inform user about prepare-frontend for missing frontend files with no flow-build-info.json
- Improve error message when stats.json is missing on production bug
- Fix typos (kudos @jhult )
- Use existing methods instead of repeating code (kudos @jhult )
- Fix a random fail test for 2.1 branch
- Review and improve DevModeHandlerTest (internal improvement)
- Iterate over copies when firing binder events
- Log a warning for obviously invalid style or class bindings
Vaadin Flow 2.1.4 is a maintenance version with the following notable fixes and enhancements:
- Added babel plugin to transpile object literal spread { ... } syntax not supported by Edge
- Deprecate MultiSelectionEvent.getNewSelection
- BundleParser incorrectly removes attribute values that contain // (double slash)
- Always consume the stdout stream from (p)npm and log at debug level
- Deprecate isSafariOrIOS
- Elide npm stdout unless command fails
- Set direction along with the Locale for the UI
- Throw if blocking on JS result would deadlock
- Find the name of the search path environment variable before manipulating it
- Use headless chrome always, except on local debug
- TreeDataProvider: Apply filters to children
Changes since 14.1.16
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
More info can be found from Here
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