A new console.error from downshift has popped up in the test reports. Not sure how to address it, as I'm not even sure how the component is switching from controlled to uncontrolled.

It's this line:

 const baseNativeProps = !value
   ? props
   : { ...omit(props, "placeholder"), value: value };

Combobox does not have use a select element inside, so it does not have this placeholder. You can just pass

          <BaseCombobox
            {...props}

The placeholder was added only for design purposes for select really. So removing it here is fine.

All in all -> I'm not sure if this combox is accessible. I had a hard time figuring out how to use it with a screenreader and I could look at it to help me understand it. I think we should check how that's usually done and recommended and see if we can support users with screen reader better. Otherwise we're improving UX for some user by removing usability for others. The fact that testing library has a problem figuring that element out is probably also not a good sign in that regard.

The downshift error may come from the fact that we set some of the defaultValues in TopicAlcRequest's useForm to undefined, and then change these values with fields that are wrapped in _Controller, kind of like what this user describes: downshift-js/downshift#478 (comment)

Additionally, there was some wrong copy pasting action in the Form Combobox component.

This commit seeks to address these issues, and I don't see the warnings any more locally. 2b3a266

Ajh lol @programmiri you commenetd about what I just pushed a commit to fix ^^

Closing as this warrants more conversation and possibly a11y fixes to the Combobox component.