Marco Collovati

> I would urge some caution with the existing GWT test Do you mean the tests `src/test-gwt/java` folder? Or also the Testbench integration tests like `DomEventFilterIT`?

> LEADING and TRAILING should always come in pairs, and INTERMEDIATE should never happen "outside" such as pair. If there's some side effect that triggers a new LEADING before without...

> I have a faint memory of such assumptions in the test-gwt folder I'll check, thanks

All reported issues with `vaadin.eagerServerLoad` do not reproduce anymore with Vaadin 24. #16498 has not been back-ported to Vaadin 23, so double initialization still happens

Could be related to https://github.com/vaadin/flow/issues/19305#issuecomment-2095273857

Flow should already print a message, but it is at TRACE level. @mvysny could you try to set TRACE level for category `com.vaadin.flow.server.communication.rpc` and check if you can see something...

It might not depend on Vaadin itself, but other servlet filters the application is using. You should double-check that all deployed filters support async.

Colon is not listed in the keycode values (https://developer.mozilla.org/en-US/docs/Web/API/UI_Events/Keyboard_event_code_values). So, this is probably the reason why there's no enumeration entry. I think the problem here is that the colon key...

The test seems stable nowadays. This issue can probably be closed

I think an explanation can be found in the documentation for [Faster Starts by Pre-Compiling](https://vaadin.com/docs/latest/configuration/development-mode#precompiled-bundle), where it is mentioned that > When customizing an in this mode, the following points...