Skip to content

Vaadin 14.3.4
Compare
Choose a tag to compare
@ZheSun88 ZheSun88 released this 24 Aug 08:34
· 14 commits to 14.3 since this release
14.3.4
c5af694
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Vaadin 14.3.4

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

Flow 2.3.4

  • Fix document link created by StreamResource in Embedded applications
  • Fix HasStyle::setClassName to work as specified in Javadoc
  • Improve log message for skipping (p)npm install
  • Make a workaround for Spring boot when getting a Logo resource URL
  • Set content type in UnsupportedBrowserHandler
  • Avoid findIndex JS Array function in VaadinDemodeGizmo
  • Extend Javadoc for Text component and clarify not-supported API
  • Don't remove child Components immediately: make checks and then remove
  • Retain Emoji characters when removing comments from JS sources

More details can be found from -> HERE

Components

  • Vaadin Date Picker
    • Avoid exception when parsing empty value
  • Vaadin Grid
    • Fix Javascript error when filtering grid with a large dataset

Changes since 14.3.3

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
Assets 2