✔️ Deploy Preview for carbon-react-next ready!

🔨 Explore the source changes: 9e4ce0d

🔍 Inspect the deploy log: https://app.netlify.com/sites/carbon-react-next/deploys/6172df20c9ab020007875efd

😎 Browse the preview: https://deploy-preview-9913--carbon-react-next.netlify.app

✔️ Deploy Preview for carbon-elements ready!

🔨 Explore the source changes: 9e4ce0d

🔍 Inspect the deploy log: https://app.netlify.com/sites/carbon-elements/deploys/6172df20c9ab020007875ef9

😎 Browse the preview: https://deploy-preview-9913--carbon-elements.netlify.app

✔️ Deploy Preview for carbon-components-react ready!
Built without sensitive environment variables

🔨 Explore the source changes: 9e4ce0d

🔍 Inspect the deploy log: https://app.netlify.com/sites/carbon-components-react/deploys/6172df203a447600074cdaef

😎 Browse the preview: https://deploy-preview-9913--carbon-components-react.netlify.app

Been thinking about this more -- we might want to use a pattern we've used elsewhere and have the disabled items not actually be disabled="true" but be disabled functionally and stylistically instead.

That way they're still able to be focused and communicate their state to the user via screen reader or whatever
that might also help with the downshift weirdness where last non-disabled hoverable item is selected if enter is pressed while hovering on a disabled item