Drupal_html_id error when used with Workbench Moderation

To enable the AJAX validation when changing the value of "Moderation state" we also need to enable the module workbench_email.

The screenshot comparing code is not from any Drupal version I know of. The relevant lines in misc/ajax.js have not been changed since 2010 and do use the same syntax as wysiwyg.js does.

drupal/misc/ajax.js lines 310-341:

Drupal.ajax.prototype.beforeSerialize = function (element, options) {
  // Allow detaching behaviors to update field values before collecting them.
  // This is only needed when field values are added to the POST data, so only
  // when there is a form such that this.form.ajaxSubmit() is used instead of
  // $.ajax(). When there is no form and $.ajax() is used, beforeSerialize()
  // isn't called, but don't rely on that: explicitly check this.form.
  if (this.form) {
    var settings = this.settings || Drupal.settings;
    Drupal.detachBehaviors(this.form, settings, 'serialize');
  }

  // Prevent duplicate HTML ids in the returned markup.
  // @see drupal_html_id()
  options.data['ajax_html_ids[]'] = [];
  $('[id]').each(function () {
    options.data['ajax_html_ids[]'].push(this.id);
  });

  // Allow Drupal to return new JavaScript and CSS files to load without
  // returning the ones already loaded.
  // @see ajax_base_page_theme()
  // @see drupal_get_css()
  // @see drupal_get_js()
  options.data['ajax_page_state[theme]'] = Drupal.settings.ajaxPageState.theme;
  options.data['ajax_page_state[theme_token]'] = Drupal.settings.ajaxPageState.theme_token;
  for (var key in Drupal.settings.ajaxPageState.css) {
    options.data['ajax_page_state[css][' + key + ']'] = 1;
  }
  for (var key in Drupal.settings.ajaxPageState.js) {
    options.data['ajax_page_state[js][' + key + ']'] = 1;
  }
};

PHP automatically turns multiple POST:ed keys with the same name ending in [] into an array once they've reached the server.

If the patch suggested here is applied it effectively adds a second parameter containing the filtered list of element ids, while leaving the original list untouched. That pretty much guarantees the server will reject the message due to the excessive amount of POST parameters, the very problem this mechanism is intended to alleviate. This is easily verified by looking at the ajax request's headers in the browser's developer tools.

Could you be more specific as to why you think Wysiwyg is involved in this, and perhaps figure out exactly how old that code sample from core was?