Closed mahotilo closed 4 years ago
If this event is useful in such implementation CustomSection:formElementsLoaded
, it can be renamed to CustomSection:formElementsAccessed
UPD Yes, we need it. So I will take a pause to propose another patch
I think it’s better to introduce the new event CustomSection:EditorLoaded
. Let CustomSection:formElementsLoaded
fires every time it happens now.
Also, with new function argument it is possible to make more detailed events, e.g. for update or saved.
gp_editor.getFormElements = function(event="CustomSection:formElementsLoaded")
doesn't look right. Looks more like PHP.
I agree, but we already have the same
And already Bunch
Hmm. Im' not sure if I already want to bind the plugin to ES6 browsers.
Seems as if Android Webview joined the party last month. Hmm, well... then. But we have to be cautious in frontend scripts
It's just because I only kicked Internet Explorer as admin browser in Typesetter 5.2-rc.
Now the
CustomSection:formElementsLoaded
event is triggered every timegp_editor.getFormElements
is called. It means when section is saved, updated and Dirty-checked. This is too often and definitely not onLoaded. I have found a new place to trigger the event only when control elements are created.