any fix for now?

any fix for now?

#5860

waiting for code review

Same issue here. Any progress on getting #5860 reviewed and/or doing a fix that resolves this holistically without the need for consumers to set an additional prop?

Same issue here.

Very much reproducible and annoying.

As far as we know from #5907 our only hope is @Methuselah96 🙏

Same issue here, that is one nasty warning for such a nested aria definition

just got stung by this.

Any solution for this? I am having the same issue in my Next15 project

Any solution for this? I am having the same issue in my Next15 project

same heere

Any solution for this? I am having the same issue in my Next15 project

Same, here is the error message I've got

This is indeed a pretty annoying error. until it is fixed, you can patch the library. go to /dist/Select-1fd588c9.esm.js and add:
componentHasMounted: false, to this.state, this.setState((s) => ({ ...s, componentHasMounted: true })) to the top of componentDidMount and then change the aria-activedescrendent check to

 'aria-activedescendant':
                    this.state.componentHasMounted && this.isAppleDevice
                       ? undefined
                       : this.state.focusedOptionId || '',

PR here

no progress on this? 2 prs opened... let me know if I can help somehow

Thank you for the wonderful library.
I apologize for taking up your time, but could you please merge the PR?

+1

+1 😢

+1

Any solution for this? I am having the same issue in my Next15 project

Same, here is the error message I've got

The errors related to the number changing in "react-select-#..." can be fixed by adding the instanceId prop.
You'll still be left with the aria-activedescendant error though. Just waiting on that PR to be merged... 👀

Holy cow, close to a year with the bug 😱

+1

+1

Still an issue, a year later

+1

+1 ( Next.js )

+1 🫣
Label for this bug should definitively be confirmed not unconfirmed by the many people confirmed this by now.

+1 nextjs 15

The bug is still happening on Next.js 15.

+1

here

@JedWatson can we please please please merge it?

+1