Confirm Semi-coupled form elements can work with autocomplete

Added a test module in the MR and found that the autocomplete inputs (which had been proven to work in the past but never got test coverage) no longer work due to the input now using the Radix TextField component. This component intercepts a few props, including className and applies them to the input's parent <div> instead of the <input/> and Drupal's autocomplete initializes based on the presence of .form-autocomplete on an <input/> element.

Between this issue and 📌 Confirm Semi-coupled form elements can work with State API visibility Active , if we want to continue using Radix we need to have a way to customize the attributes sent to the input elements within the component. I filed an issue with primitives about doing this with Checkbox, and if that is welcomed I'll do the same in Radix themes for the TextField component

This is a blocker for ✨ [PP-1] Make link widget autocomplete work (for uri and uri-reference props) Postponed .

If Radix doesn't accept the PR, is there a way we can accomplish it via ref? Does Radix already forward refs to the form element we'd want our attributes on?

It can be done with a ref!

Updated MR on the way...

I think the MR looks great. Should we upgrade to React 19 and take advantage of the nicer syntax for refs?

#13: Let's not expand the scope here. 🙏 Opened 📌 Upgrade to React 19 (and take advantage of the nicer syntax for refs Active for that ☺️

Some discoverability and consistency remarks, plus I don't understand why test is being changed. I bet it's all trivial for @bnjmnm to address 👍

Feedback addressed and the Cypress memory issue was seemingly addressed by making the test module name shorter (???)

#15: WTF?!?! 🤪

Self-addressed remaining nits. Now needs FE review.

@balintbrews approved this but it looks like we still need a semi-coupled owner to approve too> @hooroomoo seems like the best candidate for that

After a few days of e2e tests passing reliably, the autocomplete test introduced here began encountering the unpredictable+ambiguous "We detected that the Electron Renderer process just crashed.". So we can continue working without false-red-x's popping up, the autocomplete e2e test is bypassed on headless and the screenshot below shows that it is passing fine on headed.

bnjmnm → credited balintbrews → .

bnjmnm → credited hooroomoo → .

Merged. Thanks for the reviews everybody!

Automatically closed - issue fixed for 2 weeks with no activity.