Config single export JavaScript fails

Hi!

Is this issue only with single hierarchical select module enabled?

At least I could not reproduce the issue without that module.

We're seeing this issue using Chosen 4.0.3 and Drupal 11.3. We do not use the single hierarchical select module. We do have Chosen configured to "Always apply" for both single select and multi select.

For what it's worth, the suggested jQuery selector configuration workaround did not work for me.

I had to use this "starts with" attribute selector to match both of the select inputs in the core Config Export form (config_type and config_name):
select:not([name=^"config_"])

The problem described in #3571919: Comma separated selectors list limits usability limits how much that setting can be used as a workaround somewhat.

At least on Chosen 5.0.x I cannot reproduce the issue with Drupal 11.3.5

If you can, please try to upgrade to the 5.0.x branch with the https://github.com/noli42/chosen/releases/download/3.0.2/chosen-assets-v... library.

I notice a different behavior in the following two projects Drupal 11.3.7:
- a clean project (installed using "composer create drupal/recommended-project")
- a legacy project migrated from D10, with several contrib and custom modules.

In the clean project, the /admin/config/development/configuration/single/export page works correctly.

In the other project, the page above has a weird behavior: choosing a "configuration type" and then a "configuration name" doesn't work at all, and even patching as shown in https://www.drupal.org/project/webform/issues/3585180#comment-16553511 works correctly only once. Any following selection of a "configuration name", without changing "configuration type" shows empty configuration.

Anyway, if the "configuration type" is changed to another value and then set back, the "configuration name" selector works (once again, even if code is patched to avoid parsing of null yaml, it works only once).

Example:

configuration names: A, B, C
configuration types: A1, A2, A3, B1, B2, etc...

choosing A, A1-> ok*
A2 -> empty config
B,A,A2 -> ok*
A1 -> empty config

*: only if code is patched as described in the issue linked above

and so on.

Moreover, if I choose to export the whole configuration, the file is corrupted.

I've seen there have been a lot of changes in ConfigSingleExportForm, I haven't spot the root cause, but I tried to rollback the whole "config" folder under "core/modules" with the latest version from version 11.2.x (11.2.11). In this case the export works correctly.
This looks to be a regression in 11.3.x.

The problem I reported was actually due to Webform Devel module, in which there is an hook which alters the ConfigSingleExportForm.

More details here https://www.drupal.org/project/drupal/issues/3585442#comment-16555761

Any way to reproduce this issue on 5.x?