Is your feature request related to a problem? Please describe.
For proper support of multi-locale sites components that render as <a> elements should support the locale prop to allow switching the locale.
I am implementing a locale/language switcher in a Dropdown. I currently cannot use the href prop of the <DropdownItem> component because it does not support a locale attribute. Using keyboard navigation does not activate nested <Link> components so a separate onPress event was needed to achieve the desired behavior.
Describe the solution you'd like
I would like to be able to use NextUI components that are capable of rendering as <a> elements the same way I would use a <Link> component
Current work around I am using is to implement the onPress event while also leaving the <Link> component so the url will be displayed on the bottom corner of the browser when hovering over the link.
Is your feature request related to a problem? Please describe.
For proper support of multi-locale sites components that render as
<a>
elements should support the locale prop to allow switching the locale.I am implementing a locale/language switcher in a Dropdown. I currently cannot use the
href
prop of the<DropdownItem>
component because it does not support a locale attribute. Using keyboard navigation does not activate nested<Link>
components so a separateonPress
event was needed to achieve the desired behavior.Describe the solution you'd like
I would like to be able to use NextUI components that are capable of rendering as
<a>
elements the same way I would use a<Link>
componentex:
Describe alternatives you've considered
Current work around I am using is to implement the
onPress
event while also leaving the<Link>
component so the url will be displayed on the bottom corner of the browser when hovering over the link.Screenshots or Videos
No response