vaadin/flow 23.2.0.beta3

Vaadin Flow 23.2.0.beta3

on GitHub

Changes since 23.2.0.beta2

All changes

Breaking changes

• Use first deployed VaadinServlet to serve static resources (#13795)
  Commit · Pull request · Issues 14239, 13190

  Changes static files loading so that: 1. The overall behavior is reverted to that in 23.0, i.e. static files are loaded from /context/servlet/VAADIN instead of /context/VAADIN 2. When using Vite in dev mode, uses the first deployed VaadinServlet to serve static resources. If you have both a /foo/* and a /bar/*mapped servlet, then if /foo is the servlet deployed first, also /bar/ requests will use /foo/VAADIN for static resources. This reverts commit af97538 If multiple servlets are registered, use the first one If multiple mappings are present on the servlet, sort and use the first one. The servlet mappings are not returned in order so we cannot use the first registered one.

New features

• Allow to set a feature flag using a system property
  Commit · Pull request

• Give an access to ViewAccessChecker in subclasses
  Commit · Pull request

  Makes ViewAccessChecker be accessible in the VaadinWebSecurity subclasses, for example, to be able to override the security configuration for SSO.

Fixes

• Make frontend servlet check more tolerant
  Commit · Pull request

• Hange prefix to vaadin. for feature flag system properties
  Commit · Pull request

  I'm amending #14408 here. I realised that it is way more common to use dots than dashes as separator in system property names. While there is no change in functionality, I'd prefer to follow the standards.

• Not modify browser history if location has no hash
  Commit · Pull request · Issue

  if no segment with hash is present in the location, while navigating between Flow and legacy views/components, the update of the browser history is not needed.

• Initialize PwaHandler only once
  Commit · Pull request

• Execute PushRequestHandler before DevModeHandler
  Commit · Pull request

  When an application with PUSH enabled tries to re-establish the push connection after a server restart, it may happen that the dev mode handler responds to the push request with HTML contents (dev-mode-not-ready.html). In this situation, an error is shown on the browser page, a manual page reload is required to make the application work again. This changes the request handlers order so that the PushRequestHandler is executed before DevModeHandler

• Postpone http request on online listener
  Commit · Pull request · Issue

  It sometimes happens that when window online listener is invoked, http request to sw.js fails anyway with net::ERR_INTERNET_DISCONNECTED error, even if navigator.onLine flag is true. To reduce the possibility of a network failure in the online event listener, the request is postponed by a little number of milliseconds.