Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

next: Render issue when bind:open on Select.Root #1534

Closed
robinbraemer opened this issue Dec 7, 2024 · 2 comments
Closed

next: Render issue when bind:open on Select.Root #1534

robinbraemer opened this issue Dec 7, 2024 · 2 comments
Labels
status: needs reproduction A reproduction is required to support the issue.

Comments

@robinbraemer
Copy link

Describe the bug

The Select component is not rendering correctly when using bind:open.

Reproduction

<Select.Root
	bind:open={selectRegionOpen}
	type="single"
	value={cluster.regionId}
	onValueChange={(value) => handleRegionChange(cluster.id, value)}
>

image


Without bind: it renders as expected.

image

<Select.Root
	open={selectRegionOpen}
	type="single"
	value={cluster.regionId}
	onValueChange={(value) => handleRegionChange(cluster.id, value)}
>

Logs

No response

System Info

Versions:

- https://github.com/huntabyte/shadcn-svelte/tree/8b0c6d29935f6192b87f6ed5c09cbc12d436873b
- "bits-ui": "1.0.0-next.67"

Severity

annoyance

@robinbraemer robinbraemer changed the title Render issue when bind:open on Select.Root next: Render issue when bind:open on Select.Root Dec 7, 2024
@huntabyte huntabyte added the status: needs reproduction A reproduction is required to support the issue. label Dec 7, 2024
Copy link
Contributor

github-actions bot commented Dec 7, 2024

Please provide a reproduction.

More info

Why do I need to provide a reproduction?

This project is maintained by a very small team, and we simply don't have the bandwidth to investigate issues that we can't easily replicate. Reproductions enable us to fix issues faster and more efficiently. If you care about getting your issue resolved, providing a reproduction is the best way to do that.

I've provided a reproduction - what happens now?

Once a reproduction is provided, we'll remove the needs reproduction label and review the issue to determine how to resolve it. If we can confirm it's a bug, we'll label it as such and prioritize it based on its severity.

If needs reproduction labeled issues don't receive any activity (e.g., a comment with a reproduction link), they'll be closed. Feel free to comment with a reproduction at any time and the issue will be reopened.

How can I create a reproduction?

You can use this template to create a minimal reproduction. You can also link to a GitHub repository with the reproduction.

Please ensure that the reproduction is as minimal as possible. If there is a ton of custom logic in your reproduction, it is difficult to determine if the issue is with your code or with the library. The more minimal the reproduction, the more likely it is that we'll be able to assist.

You might also find these other articles interesting and/or helpful:

@huntabyte
Copy link
Owner

I need a minimal reproduction to debug, a snippet of the Select.Root component won't suffice as I'm not able to reproduce by simply binding

@huntabyte huntabyte closed this as not planned Won't fix, can't repro, duplicate, stale Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: needs reproduction A reproduction is required to support the issue.
Projects
None yet
Development

No branches or pull requests

2 participants