You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This way you don't have to worry about managing the aria-* attributes yourself. In the future we probably will accept and prefer incoming aria-* props instead of the ones that we know about. This could lead to incorrect links between controls and labels/descriptions if you are not careful, but it would be a way to override the values we know about.
The reason it is currently not rendered on the Button is because we override it with an internal value (which is currently not defined because no Field was used, the moment you use a field it will prefer that value over the incoming value). Again, I think we will accept and prefer aria-* props in the future if there is a need for this.
Going to close this for now, but let me know if you really want to use custom aria-* props instead 👍
What package within Headless UI are you using?
@headlessui/react
What version of that package are you using?
0.0.0-insiders.dcbcd79
What browser are you using?
Chrome
Reproduction URL
https://codesandbox.io/p/sandbox/amazing-glitter-forked-ctqf7f?file=%2Fsrc%2FApp.tsx%3A13%2C25
Describe your issue
Notice that the
aria-describedby="description"
attribute onListbox.Button
is not rendered.However, if I add
as={Fragment}
toListbox.Button
and put the attribute on the child<button>
, then it is rendered correctly.The text was updated successfully, but these errors were encountered: