- 🇸🇰Slovakia poker10
Regarding the comments #19, #13 and #12, I think that probably this: ✨ Make sending ajax_html_ids optional Needs review could be a more feasible approach in this D7 stage (though it is not a fix, only workaround).
In certain large and/or complex forms (entity) or other, which involve a number of elements etc it is sometimes the case that ajax_html_ids causes the number of variables in the ajax postback to exceed 1000 resulting in partial loss of postback data. In some scenarios this can cause the ajax postback in admin forms to fail validation of the theme / theme token resulting in additional processing being run on the form where mandated via the non-admin theme and potentially causing WSOD / calls to functions not loaded.
The core function drupal_html_id will look for the ajax_html_ids attribute of the post-back, and already has a case to validate if there is a ',' and to explode the entered string - I propose making this the standard operating procedure.
If the misc/ajax.js were to always flatten the values into a comma delimetered string, there is a very large number (in some cases) of input variables that will not be run:
Current callback:
ajax_html_ids[]=id_one
ajax_html_ids[]=id_two
ajax_html_ids[]=id_three
vs.
ajax_html_ids=id_one,id_two,id_three
Needs review
7.0 ⚰️
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Regarding the comments #19, #13 and #12, I think that probably this: ✨ Make sending ajax_html_ids optional Needs review could be a more feasible approach in this D7 stage (though it is not a fix, only workaround).