Skip to content

Releases

Vaadin Framework 7.7.56

Choose a tag to compare

@mlindfors mlindfors released this 13 Nov 13:48
b167d99

The Vaadin Framework 7.7.56 is an extended-support release with the following changes:

  • The framework will now ignore the disconnect of stale push resources after reconnect. This means that the Push connection will properly re-establish itself after a network interruption.
  • There will now be a warning about JEP 500 violations.
  • Added BOM convergence validation tooling to keep dependency versions in line.
  • The license checker now also supports distribution keys. Read more about license validation on production servers here.

Vaadin Framework 8.32.3

Choose a tag to compare

@thevaadinman thevaadinman released this 30 Oct 21:02
b167d99

Vaadin Framework 8.32.3 is an Extended Maintenance update release with the following changes:

  • Added support for runtime licenses, aka. Distribution Keys, which will allow you to distribute a Vaadin application built with an Extended Maintenance version without having to expose a developer key.

    Read more about this feature on Vaadin Docs.

  • Fixed a race condition in Push where a PushConnection would close permanently instead of being resumed when a client temporarily loses network connectivity.

    As this issue is caused by a race condition, it would manifest in a nondeterministic manner, and as such flew under the radar for a long time. It was originally reported as Flow issue #26689.

Vaadin Framework 7.7.55

Choose a tag to compare

@thevaadinman thevaadinman released this 14 Oct 10:29
d07721b

Vaadin Framework 7.7.55 is an extended support release with the following change:

Vaadin Framework 8.32.2

Choose a tag to compare

@thevaadinman thevaadinman released this 12 Oct 12:12
eb162ee

Vaadin Framework 8.32.2 is an Extended Maintenance update release with the following changes:

  • Disabled Atmosphere's CORS header interceptor for security. Backport of Flow PR #26215. Fixes issue #26214.
  • Prevented session lock from leaking if an invalid UI ID was provided in a request from the client to the server to eliminate a potential denial of service vector.

Vaadin Framework 8.32.1

Choose a tag to compare

@thevaadinman thevaadinman released this 14 Sep 13:04
b6da8b0

Vaadin Framework 8.32.1 is an Extended Maintenance update release with the following change:

  • Updated JSoup from version 1.15.3 to 1.23.2 to address CVE-2026-71497.

    This should be an invisible change to users; however, the behavior of JSoup has changed between versions in a way that might require changes to some files. Namely, self-closing tags are not allowed when parsing in an HTML context.

    If you experience issues regarding HTML content or Designer templates with self-closing tags, let us know by filing an issue with Vaadin Support.

Vaadin Framework 7.7.54

Choose a tag to compare

@mlindfors mlindfors released this 11 Sep 18:37
f5be39f

The Vaadin Framework 7.7.54 is an extended-support release with the following changes:

  • The jsoup version being used has been updated to 1.23.2. This new version will change how it handles self-closing tags for components.
  • Bundle-RequiredExecutionEnvironment has been updated to JavaSE-1.8
  • Made the maximum request body size configurable. This is intended to be an anti-(D)DOS measure.
  • Moved blocking calls outside session lock as a possible deadlock mitigation measure.
  • Made it possible to override ServerRpcHandler creation in PushHandler.

Vaadin Framework 8.32.0

Choose a tag to compare

@thevaadinman thevaadinman released this 17 Aug 13:19
646a915

Vaadin Framework 8.32.0 is an Extended Maintenance release with the following changes:

  • Added URL scheme validation in ExternalResource and Page. Based on concepts introduced in Flow PRs #24539 and #24943.

    This is an optional (disabled by default) security feature that allows enabling and configuring a list of safe URL schemes in order to block a class of attack where a normal link to a resource could be manipulated to execute JavaScript or make users grant access to any privileged resources accessible through a URL scheme.

    When enabled with the safeUrlSchemes configuration parameter, all uses of ExternalResource (including Image and downloads) as well as Page#open and Page#setLocation will be validated against a list of valid URL schemas.
    Alternative constructors and methods are provided for bypassing the validation on a case-by-case basis.

    In Vaadin versions 25.2+, the default set of safe URL schemes are http, https, mailto, tel and ftp. Script-capable schemes such as javascript and data are intentionally left out.

    To enable URL scheme validation with the default set of schemes, set the configuration parameter safeUrlSchemes with no value. To provide your own list of safe URL schemes, set the parameter's value to a comma-separated list of URL schemes you wish to allow. Relative URLs are always considered safe.

  • Added API for controlling the behavior of Grid's layout-after-scroll behavior when using Component Renderers.

    This was a problem mitigation feature added in Vaadin 8.25.0 in order to fix issue #12608. In the release notes, we asked for people to contact Vaadin Support in case they experience severe performance degradation, as the full layout operation could get heavy in complex Grids. This resulted in issue #12680.

    The API introduces the enum Grid.LayoutAfterScrollMode with the values AUTOMATIC, ALWAYS and NEVER, along with the following functions:

    • void Grid#setLayoutAfterScrollMode(LayoutAfterScrollMode)
    • LayoutAfterScrollMode Grid#getLayoutAfterScrollMode()
    • boolean Grid#isLayoutAfterScrollActive()

    You are encouraged to read the JavaDoc for those functions for more information. In short, LayoutAfterScrollMode.AUTOMATIC is now the default, and it disables the layout-after-scroll pass if only simple, "scroll safe" components are used in Grid, and if any component outside of that list is used, enables the mitigation. Depending on need, users can set the mode to ALWAYS (where the mitigation is always active as long as any component renderer is used; this is how it worked previously) or NEVER, which disables the mitigation.

    You will need to configure the behavior on a per-Grid basis. There is currently no way to change the set of "scroll safe" components.

  • Added a configuration parameter to control the maximum request body size.

    The parameter maxRequestBodySize can be set to a numeric value (in bytes) or -1 to disable the limit. The default is 10 megabytes. This affects the maximum size UIDL, RPC and Push request bodies. Does not affect uploads.

    If the request size exceeds the limit, the Framework rejects the request with a HTTP 413 (Request Entity Too Large) code. This is intended as an anti-(D)DOS measure. For more information, read the JavaDoc of Constants.SERVLET_PARAMETER_MAX_REQUEST_BODY_SIZE.

    This is a backport of Flow PR #24866.

  • Replaced GWT's Window.ClosingHandler functionality with a custom implementation in order to remove dependency on the HTML unload event.

    The unload event is deprecated and will make modern browsers complain about its usage, or may outright disable functionality depending on it. Vaadin Framework uses it to detect when a browser window is closed, so that sessions can be cleaned up, etc. GWT has deprecated the functions related to window closing and may remove them in the future. Vaadin Framework now uses a custom pagehide event hook.

    The version of GWT shipped with Vaadin 8 still hooks functions to window.onunload, which will cause browsers to warn about it, but this should not break functionality. In order to get rid of the warning browser-side, update to a GWT version >=2.12.0 by updating your project's dependencies as described in this article by Tatu Lund.

  • Unified response headers with current Flow behavior. In practice, removed Content-Type headers and one unnecessary Cache-Control header from heartbeat traffic. See Flow PR #23225.

  • Removed the org.reflections.reflections dependency from vaadin-portlet and updated its version from 0.9.11 to 0.10.2 in vaadin-server.

Vaadin Framework 7.7.53

Choose a tag to compare

@mlindfors mlindfors released this 17 Jun 11:35
02c87d4

The Vaadin Framework 7.7.53 is an extended-support release with the following changes:

  • The framework now uses 403 FORBIDDEN instead of 410 GONE when the session has expired.
  • Added a missing OSGi dependency to the license checker.

Vaadin Framework 8.31.1

Choose a tag to compare

@thevaadinman thevaadinman released this 28 Apr 08:38
fa8613e

Vaadin Framework 8.31.1 is an Extended Maintenance update release with the following change:

  • Added caching to ConnectorTracker's update operations to speed up component hierarchy visibility changes. This change adds a minor temporary memory usage penalty but reduces the total amount of checks performed to about 9% of previous values and helps speed up heavy UI updates significantly.

Vaadin Framework 7.7.52

Choose a tag to compare

@mlindfors mlindfors released this 14 Apr 12:58
3e64b6a

The Vaadin Framework 7.7.52 is an extended-support release with the following changes:

  • Fixed a client side crash in ResponsiveConnector.

    • Execution would fail if a CSS rule did not have the selectorText property set. This change handles the unset property gracefully.
  • Improved license checking strategy.

    • License checking is now performed more consistently during development. If an application built with Vaadin 8.31+ is deployed in a production environment without a valid license key present, an error event is logged.

    Read more about license validation on production servers here.