`inputRef` prop being passed into DOM when using <Dropdown /> about design-system HOT 6 CLOSED

Fixed in #2566

from design-system.

+1. Just confirming that we're seeing this issue in MCT after upgrading to MGov DS v8.1.1

from design-system.

@austindh and @Josh68, what are your apps currently using the inputRef for? Focus management?

from design-system.

Yes, for focus management. We use it to focus on the dropdown if the user attempts to continue without making a selection.

from design-system.

I'm actually seeing similar warnings on Autocomplete, with focusTrigger and labelId. In this case, these aren't even props we're passing in. The warnings are being generated just because we're using the DS component.

For inputRef on the Dropdown (at least in one place) we're using it to programmatically keep multiple parts of the UI in sync (can't elaborate more than that without digging in further).

We did not see these errors before the upgrade to DS V8, AFAIK.

from design-system.

Good information. Thanks, all! We do have an autoFocus prop for putting focus on the component, but I realize there might be situations where inputRef is easier to use. CC @forrestbaer and @zarahzachz

The Autocomplete warnings I think we've addressed in the current beta version, but overall we can do more to clean up props and make them consistent.

from design-system.