Open mlopezFC opened 3 years ago
See e.g. https://github.com/vaadin/flow/issues/9768 for more information. It's possible that such a round-trip is done here as well.
With Vaadin 24.3.9 the example snippet is now returning false in both cases.
If, however, you go and change the rte.asHtml().setValue("<p>Test</p>");
to rte.asHtml().setValue("Test");
, you get two value change events, where the second one is reportedly coming from the client. Of course you shouldn't be pushing broken values into the thing to begin with, so I don't know how big of an issue this actually is.
Description
In a value change listener, the property fromClient in the event will return true when the modification is being made by the server side.
Expected outcome
The property fromClient should return false, given that the change was originated from the server side.
Actual outcome
The property will return true
Minimal reproducible example
This example shows that a TextField will return the opposite under the same conditions:
Steps to reproduce
Clear steps describing how to reproduce the issue.
Environment
Browsers Affected