Machine name JS does not work in Page Data/Component Instance form

🤔 Which field type's widget uses this?

AFAICT this is about \Drupal\Core\Render\Element\MachineName, which is a FormElement plugin, not a FieldWidget plugin.

Per #2, unless I'm wrong, this would be the appropriate issue queue component. 🤓

Unfortunately we hit this right away when integrating webform with XB. As explained in the issue summary entering the machine name in the block prop works, but not the autocomplete. Unfortunately it is loaded back as a Title (machine_name) so when/if you edit it you need to remember to edit it back to machine name only.

I opened 🐛 Autocomplete machine name handling does not match to machine name Active for that but is a duplicate.

Ben tells me this is a different issue, so reverted to what it had before I took it over, so this problem is still being tracked. Adding back the reference though to make sure that is not forgotten.

@gábor hojtsy I believe you were able to workaround this problem by changing to use a select? Would that be acceptable for Drupal CMS 2.0?

It's also unclear to me how does machine name JS relate to the autocomplete which is shown in the video 🤔 Keeping the stable target tag for now so this doesn't get lost.

It's possible this works after 📌 Redux-aware form input components should be aware of direct element manipulation Active landed, which adds support for our inputs directly changing value via DOM or jQuery methods and triggering a redux/preview update.

The webform related problem was diagnosed by the XB team as related to the block form validate/submit handlers not being called, because when the autocomplete shows up, it returns the right value, but on save it does not save the converted internal machine name. That is dealt with in 📌 ComponentSourceInterface::submitConfigurationForm and validateConfigurationForm are never called Active (but is not yet working).

Ah, #11 I think this is additional confusion regarding machine name JS vs autocomplete

• the logic in machine-name.js, which is why I filed this issue, is likely addressed in #3537872, which was mentioned in #10
• Entity Reference value conversion, which is the symptom mentioned in #6 (and in the case of webform is working with machine name values) should be solved in #3523496.

I think I contributed to this initial mixup, but fortunately all of these problems are nearly or already fixed.

I can confirm what @bnjmnm wrote in #12! :D

But there is one remaining problem discovered by @mayur-sose — see #3523496-40: Block component instance form values not processed by validation/submit handlers → .

I discussed this issue with @bnjmnm. I believe the correct status of this issue is "duplicate" because per #12.1 it was a symptom of 📌 Redux-aware form input components should be aware of direct element manipulation Active which got fixed.

However, this issue was not the one encountered by the Webform block. Instead, Webform was running into 🐛 Autocomplete machine name handling does not match to machine name Active , which was a symptom of 📌 ComponentSourceInterface::submitConfigurationForm and validateConfigurationForm are never called Active so is correctly marked as a duplicate of that one.

Unrelated to either this issue or to 🐛 Autocomplete machine name handling does not match to machine name Active , there is a remaining bug described in #3523496-40: Block component instance form values not processed by validation/submit handlers → .TC3. @bnjmnm is working on diagnosing that one and will open a new issue for it based on what he learns.