Adding a disabled date picker logs warnings
Artur- opened this issue · comments
[http-nio-8080-exec-878] WARN com.vaadin.flow.server.communication.rpc.MapSyncRpcHandler - Property update request for disabled element is received from the client side. The property is 'value'. Request is ignored.
[http-nio-8080-exec-878] WARN com.vaadin.flow.server.communication.rpc.MapSyncRpcHandler - Property update request for disabled element is received from the client side. The property is 'opened'. Request is ignored.
Closing as duplicate of vaadin/flow#8848 which will be soon fixed by vaadin/flow-components#512.
@web-padawan I'm not entirely sure if this is actually fixed by vaadin/flow-components#512 as I didn't test this - to my understanding, if the property ^ defaults are wrong on the server side, then this will be still logged.
The fix I did was taking care of two empty client->server RPC calls done with executeJS
that were not even needed, related to overriding client side validation behavior.
Thanks. I will double check when the fix is merged. Not sure if we should reopen this and mark as a bug?
I'll check it later today based on my changes. If it is still valid, yes then it should be treated as a bug as it gives a bad impression.
I can confirm that after vaadin/flow-components#512 there were no warnings logged for a disabled DatePicker
, so this can remain closed.
Thanks for checking this issue 🙇♂️