Marco Collovati

The problem here is that during a reload, there are requests incoming before VaadinService completes its intialization. Dispatching requests to a servlet before `HttpServlet.init()` is invoked seems a bit weird...

A simple "fix" is to initialize `WebIconsRequestMatcher` in `RequestUtil.isCustomWebIcon()` only if `VaadinService` is available. The drawback is that until we get `VaadinService`, the requests for PWA icons will not be...

I have no quick alternatives in mind right now. Maybe generating the icons at frontend build time and storing the paths somewhere so that the registry could read the list...

The issue is not limited to the `LitRender`, but can happen with all kind of renderers. For example adding a column with a `ValueProvider` that throws an exception (so using...

@AB-xdev did you perhaps upgraded to the latest Vaadin version? It contains a couple of fixes that prevents some of the causes of the resynchronization issue

I close the issue as there have been no updates for a while and several fixes for related issues have been released. @AB-xdev please comment here or open a new...

It seems the issue has been resolved by #15517 Cannot reproduce anymore with 14.9.5, 23.3.3 and 24.0.0.alpha9

It is really weird that the header values are encoded. Is the servlet container directly exposed to the client, or is there something in the middle that may modify the...

@mstahv @Legioth I'm working on the tests for this fix and I have a couple of question about the behavior we expect after this change is applied. I don't know...

@mstahv Thanks for clarification! The current fix works for LAZY and TIMEOUT value change mode, and it should at least fix #14090 (needs some code cleanup) I propose to focus...