Mikhail Shabarov

Could you try with a newer versions of Vaadin? The latest one is 14.8.14 https://github.com/vaadin/platform/releases/tag/14.8.14 .

We've recently updated all maintained Flow versions with Jsoup `1.15.3`. As we couldn't reproduce the issue, we assume that the issue is fixed in the later version of Jsoup. Please...

LGTM as well.

@obfischer thank you for creating an issue! > Currently I add validators via Binder#withValidator() to the binder before I all Binder#bindInstanceFields() could you please give a code example to us...

@sandronm We have no plans to pick it in the nearest future, as well as no plans to include it into V23.3. Vaadin 24 would be a good candidate to...

@taefi I propose to close this PR, some tests are failing and probably there is no big profit for us to change the build tool in tests.

Steps 1-3 give me a bit different errors: My project directory name is `special-chars-äbc`. when running with `mvn`: ``` [ERROR] Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:2.5.4:run (default-cli) on project special-char: Could...

Another JVM crash case: ``` [09:14:33][Step 7/11] ------------------ Starting Frontend compilation. ------------------ [09:14:36][Step 7/11] (node:24169) [DEP0131] DeprecationWarning: The legacy HTTP parser is deprecated. [09:14:36][Step 7/11] ? ?wds?: Project is running...

One more JVM crash case: [Flow_Public_Flow_Pull_Requests_Run_Validation_18874 (1).log](https://github.com/vaadin/flow/files/7126598/Flow_Public_Flow_Pull_Requests_Run_Validation_18874.1.log)

After this feature applied, we also need to update the following article to not mention the deprecated adapter, but describe a new approach https://vaadin.com/docs/latest/security/enabling-security