[TYPO3-core] RFC: #9562: Feature: onChange has no effect

[Dan Osipov]

That's not what the RFC does though.

The RFC adds the requestUpdate functionality to IRRE fields. The 
bugtracker entry might be a bit confusing as I was searching for 
different ways to refresh fields.

The onChange option for normal fields is one of the byproducts, that can 
be removed. If you decide it creates confusion, I'll remove it - the 
rest of the patch stays.

I spoke to Olly during the last bug day, and he said he will probably 
refactor this patch. He also gave me some pointers, which I can 
implement in the next version of this patch. I will also remove the 
onChange functionality.

Dan Osipov
Calkins Media
http://danosipov.com/blog/

Dmitry Dulepov wrote:
> Hi!
> 
> Benjamin Mack wrote:
>> What's the state of this RFC?
> 
> It should be canceled because "onChange" works only in flexforms by design. We could change the design but than we create another problem: we get a duplicate functionality in regular forms. It also breaks one of the usability laws: "One way to do one task".
> 
> According to design "requestUpdate" is available for normal forms only. It is not available in flexforms because flexforms do not have "ctrl" section. In flexforms we added "onChange" for each field. Adding "onChange" to regular forms makes "requestUpdate" questionable ("What should I use: requestUpdate or onChange? What's the difference? Why there are two different ways to make the same thing?"). At the same time flexforms will not get any equivalent of "requestUpdate", so the logic is still broken.
> 
> I suggest to keep it as it is now and cancel the RFC.
>