Leif Åstrand

As a workaround, you could try creating a regular element as a wrapper, and then do `element.setProperty("innerHTML", svgString);`

> Someone found any hack/solution/workaround for this problem? https://github.com/vaadin/flow/issues/2842#issuecomment-341652190

We could even go one step further. We're already parsing the HTML on the server so we could explicitly look for usage of `` and throw an exception saying that...

Alternatively, there could be a helper in `QueryParameters` for the most common case of getting a single parameter value. With that, your code example could be reduced to ```java String...

I'm afraid the solution isn't as easy as you describe it here (or then I'm missing some very essential detail). The restriction here isn't the the event dispatcher itself but...

Most of your assumptions are based on the traditional event loop that is used in most desktop GUI frameworks and game engines. In simplified terms, the traditional event loop looks...

> If the internals of the ED are available somewhere, I'll gladly study them and try to be more specific... It's all open source software, so feel free to go...

> BTW: Is there any documentation available about this? Unfortunately not.

There's some merit to `QueryParameters` being immutable. There could still be mutators but they would then return a new immutable object instead of modifying the existing ones. Your usage example...

`runWhenAttached` is a low-level tool that is quite tedious to use correctly since you often must take into account the possibility that the node becomes detached again before pending changes...