Vaadin 17.0.11

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 17.0 in GitHub releases, including new features, getting started, supported browsers and other technologies, and migration notes.

Visit vaadin.com to get started.

New and Noteworthy

Here are the highlighted new and improved features in this maintenance release.

Flow 4.0.8

Bug Fixes:

• Fix a bug that VaadinRequest is not available in the endpoint
• Optimize handling of requests containing Range header
• Stop logging error when updating dev dependencies

Others:

• Remove the getIndexHtmlResponse method from IndexHtmlRequestHandler, which was intended for internal use only and is no longer needed.

Changes in Flow Components from 17.0.10

Changes in vaadin-grid-flow

• Fixes:

  • ⧉ Not to call count callback for lazy Grid with multi-select. PR:433. Ticket:411

    Selecting any row of the Grid with lazy loading and multi-select mode does not trigger the count callback to be invoked. Instead, it gets the item count from the cache for defined item count, and doesn't show the select all checkbox at all and skips checkbox state update for unknown item count. (cherry picked from commit 030ef437376efea972afdcd50c80d3e58d52a873)

Changes in vaadin-text-field-flow

• Fixes:
  • ⧉ Use the same email pattern as in Flow (17.0). PR:444

Changes since 17.0.10

• Vaadin Flow (4.0.8)
• Vaadin Grid (Flow integration 6.0.8, web component v5.7.7)
  • Grid
  • Tree Grid
  • Grid Context Menu
• Vaadin Text Field (Flow integration 4.0.3, web component v2.7.2)
  • Text Field
  • Text Area
  • Password Field
  • Big Decimal Field
  • Email Field
  • Integer Field
  • Number Field
• Vaadin Themable Mixin (web component v1.6.2)

Support

Vaadin 17 is supported for one month after Vaadin 18 has been released. The latest LTS (long term support) version is Vaadin 14. More details of our release model are available on our roadmap page.

Vaadin also provides commercial support and warranty.

Getting Started with Vaadin

App starters

The best way to get started with Vaadin 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