github vaadin/platform 14.4.6
Vaadin 14.4.6

latest releases: 24.5.0.beta3, 24.5.0.beta2, 23.5.6...
3 years ago

Vaadin 14.4.6

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.

Changes in Flow Components from 14.4.5

Changes in vaadin-date-picker-flow vaadin-date-time-picker-flow vaadin-radio-button-flow vaadin-text-field-flow vaadin-time-picker-flow

  • Fixes:
    • Fix client side validation overriding (#512) (CP: 14.4). PR:549. Ticket:8848

    • Fix client side validation overriding. PR:512

      The workaround for overriding the client side validation for certain components was causing an unnecessary roundtrip to the server side, which also caused two warnings to be logged by Flow each time a disabled or a readonly component was added to the UI. The warning happened twice since two executeJS calls were enqueued: one immediately, and another when attached. Apparently there was no good reason for this behavior. This fix will only apply the executeJS once when the component is attached and it will not require a separate roundtrip to workaround the client side validation overriding the invalid value because the JS execution is enqueued on the "beforeClientResponse" phase when the server side invalid value has been resolved and can be used in the JS execution. Further improvement would be to move the FieldValidationUtil to its own module and reused from there, but that is left for later (?).

    • Use previous API to check if it is attached

Changes in vaadin-grid-flow

  • Fixes:
    • Revert ensure first page is loaded; ignore test till fixed (#551). PR:563

Changes since 14.4.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.

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

Don't miss a new platform release

NewReleases is sending notifications on new releases.