Skip to content

Conversation

@songlairui
Copy link

Problem

The __selectScope property was not being passed through to PopperContent, causing scope-related errors when using custom scopes with Select components.

Root Cause

The spread operator ...contentProps was inadvertently filtering out the __selectScope property, which is required for proper component scoping in Radix UI primitives.

Solution

Updated the component to explicitly pass __selectScope to PopperContent, ensuring proper scope inheritance.

Use Case

This fix enables the following pattern to work correctly:

import * as SelectPrimitive from "@radix-ui/react-select";

function MySelect(props: any) {
  const scope = useComposedScopes();
  return <SelectPrimitive.Root {...scope} {...props} />
}

@changeset-bot
Copy link

changeset-bot bot commented Sep 3, 2025

🦋 Changeset detected

Latest commit: cc41c2d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@radix-ui/react-select Patch
radix-ui Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

the attrs below (...contentProps), lost '__selectScope'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant