Vaadin 14.4.10

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

Vaadin Flow (2.4.9)

• Fixes:

  • ⧉ Close InputStream properly in FrontendUtils. PR:10315 Thanks to @knoobie for contribution

    Close InputStream for stats.json obtained from classpath, external url or webpack.

  • ⧉ Cache stats.json loaded from class path. PR:10303 Thanks to @knoobie for contribution

    Caches stats.json file loaded from class path and improves the performance by not being opening too many stats.json files under the load.

  • ⧉ FrameworkUtil class presence doesn't mean OSGi. PR:10285

    Make OSGi check more correct otherwise the code works incorrectly if FrameworkUtil is present in the classpath

  • ⧉ Support Java 16 for production build (#10231). PR:10236. Ticket:10115

    Updates bytebuddy dependency from 1.10.9 -> 1.10.21

  • ⧉ Avoid exposing ServletContext resources via StaticFileServer when Servlet is registered with Http Whiteboard in OSGi. PR:10268. Ticket:10260

    Note: existing Vaadin OSGi projects which map the VaadinServlet using Http Whiteboard will have to explicitly register the frontend resources starting from this release as shown in the following snippet (for more details about OSGi resource registration in Vaadin 14 , visit the documentation):

    @Component(service = FrontendResources.class)
    @HttpWhiteboardResource(pattern = "/frontend/*", prefix = "/frontend")
    public class FrontendResources {

    }

Components

Changes in vaadin-grid-flow

• Warranty Fixes:
  • ⧉ Do not throw, but log error message as this can happen naturally. (#659) (CP: 14.4). PR:704. Ticket:1884

Changes in vaadin-text-field

• fix: 'iron-resize' event when height changes is now composed

Changes in vaadin-menu-bar

• Warranty Fixes: Responsive overflow feature doesn't work correctly without percentual width
• Changing items leaves ellipses button that points to old item

Vaadin Multiplatform Runtime

• Warranty Fixes: Regression: MPR v2.0.6 does not work with IE11

Changes since 14.4.9

• Vaadin Flow (2.4.9)
• Vaadin Multiplatform Runtime (Prime) for Framework 7 (2.0.7)
• Vaadin Multiplatform Runtime (Prime) for Framework 8 (2.0.7)
• Vaadin Combo Box (Flow integration 3.2.8, web component v5.4.7)
• Vaadin Date Picker (Flow integration 2.2.6, web component v4.4.1)
• Vaadin Date Time Picker (Flow integration 1.2.7, web component v1.4.0)
• Vaadin Grid (Flow integration 4.3.9, web component v5.7.9)
  • Grid
  • Tree Grid
  • Grid Context Menu
• Vaadin Login (Flow integration 2.2.4, web component v1.2.0)
• Vaadin Menu Bar (Flow integration 1.2.4, web component v1.2.2)
• Vaadin Select (Flow integration 2.2.4, web component v2.4.0)
• Vaadin Text Field (Flow integration 2.3.6, web component v2.8.4)
  • Text Field
  • Text Area
  • Password Field
  • Big Decimal Field
  • Email Field
  • Integer Field
  • Number Field
• Vaadin Time Picker (Flow integration 2.3.7, web component v2.4.0)
• Vaadin Grid Pro (PRO) (Flow integration 2.2.5, web component v2.2.2)
• Vaadin Rich Text Editor (PRO) (Flow integration 2.3.5, web component v1.3.0)

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