Artur

The best solution though would be to proxy the websocket connection also so the Vite server remains an internal detail and no configuration is needed

Is `VaadinServletContext` a singleton? Otherwise locking will have no effect

The locking in `FeatureFlags` looks wrong. It wants to lock to avoid creating `FeatureFlagsWrapper` multiple times. The normal pattern for that would be something like ``` FeatureFlagsWrapper attribute = context.getAttribute(FeatureFlagsWrapper.class);...

Previously discussed in #1097. Not sure if the namespace is still an issue also

A quite straight forward way is to create the SVG using `LitElement`, create a Java class for it and pass dynamic data through properties, as done e.g. in here 1....

One persons bug is always another persons feature... Is the problem here that you want to forward websockets to another server using an Apache 2 configuration? Isn't that doable now...

So should we add a "feature" flag to get the old mapping back and then remove the flag in V24, as the main/only reason for returning the old mapping would...

The code that ignores the error is here https://github.com/vaadin/flow/blob/master/flow-tests/vaadin-spring-tests/test-spring-security-flow/src/test/java/com/vaadin/flow/spring/flowsecurity/AbstractIT.java#L48 The difference is that now there seems to be a `?continue` query parameter on the URL

Probably introduced by https://github.com/spring-projects/spring-security/commit/f84f08c4b9da4f326de1fed2772ae5e582d7cdf7 / https://github.com/spring-projects/spring-security/issues/11757 which is not very descriptive

You can use `import` syntax even if the modules are written as common js. Your project seems to work if you replace the `require` statements with ``` // @ts-ignore import...