updateValue() not called on content change when wrapped in aCustomField

[SonReimer]

When putting TinyMce in a CustomField to add some feature like label, tooltip etc.,
someone has to add a ValueChangeListener to TineMce calling CustomField.updateValue() to propagate values from TinyMce to CustomField.
This is not intuitive and differs from the documentation of CustomField (see comments from Martin Vysny)
I think this is because client side throws a tchange event instead of change !?!
TinyMce 4.1.3/Vaadin 24.3.2

[mstahv]

Do you have a code snippet available that could be used to reproduce the issue?

[SonReimer]

Here it is:
If you remove the ValueChangeListener in TineMceField.java:10, user changes in the editor will not be shown in Notification when closing.
MainView.java.txt
TinyMceField.java.txt

[mstahv]

Verified.

But I gotta say I'm quite surprised by the behaviour of CustomField. This described behaviour seems to depend on propagated change events withtin the custom field (that might contain a dozen of fields). I'd even go as far as claiming that it is a bug, as it might easily be there are obsolete value changes and unexpected side effects now happening. Consider some custom field having a filtering input -> there will be a ton of extra traffic and JVM execution. Might even explains some weird behaviour I recently had in one of my apps, but didn't debug further...

If/as the workaround is so simple, I'll leave this open for now before investigating further.

And cheers to @mvysny !

On a related topics. Whic are all field features you'd like? tooltip and label mentioned.

[mstahv]

Checked that at least the #28 is again broken if wrapped in CustomField (yet another webcomponent). I'd suspect that is somethign related to Dialog not to this component, similar hack to CustomField might do it 🤷‍♂️ Maybe it would be easier to implement those features directly to this component, not sure.

[SonReimer]

I think label and tooltip are sufficient. From my point of view placeholder and helper do not really make sense.

[SonReimer]

Using the mentioned workaround for updateValue() is sufficient for me.

[jcgueriaud1]

I've created a ticket for the CustomField: vaadin/flow-components#7108

The default way to synchronise the value is on change and I think TinyMceField doesn't send this event.
I think that could be an enhancement for the field (to use the change, input, timeout event instead of custom event like tchange).

But even with this that would not fit if you want to change to a different valuechangemode for the custom field.

Technically call updateValue is not a workaround for the CustomField that's how it has been designed if you don't want to synchronise the field on change.