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

rx.set_clipboard broken in 0.5.0 #3308

Open
greenseeker opened this issue May 15, 2024 · 6 comments
Open

rx.set_clipboard broken in 0.5.0 #3308

greenseeker opened this issue May 15, 2024 · 6 comments
Labels
bug Something isn't working needs investigation

Comments

@greenseeker
Copy link

greenseeker commented May 15, 2024

Describe the bug
After updating to 0.5.0, rx.set_clipboard produces a runtime error.

To Reproduce
Steps to reproduce the behavior:

def p_just_copy() -> rx.Component:
    return rx.button("copy", on_click=rx.set_clipboard("AAAAAAAAAAAAA"))

app = rx.App(
    theme=rx.theme(
        appearance="dark"
    )
)

app.add_page(p_just_copy, route="/")

Click the copy button to produce the error in the screenshot below.

Expected behavior
Set clipboard content to the given text.

Screenshots
image

Specifics (please complete the following information):

  • Python Version: 3.11.6
  • Reflex Version: 0.5.0
  • OS: Ubuntu 23.10
  • Browser (Optional): Brave 1.65.126, Firefox 125
@greenseeker greenseeker added the bug Something isn't working label May 15, 2024
@ElijahAhianyo
Copy link
Collaborator

can you run reflex init and if that doesn't fix it, try deleting your .web folder and try again

@greenseeker
Copy link
Author

@ElijahAhianyo no change, unfortunately. Is there any logging that might help?

@picklelo
Copy link
Contributor

@greenseeker what browser are you using? It's working on my Chrome and Safari. I wonder if this may be related.

@greenseeker
Copy link
Author

@picklelo reproduced in Brave 1.65.126 and Firefox 125

@greenseeker
Copy link
Author

Since updating to 0.5.1, I'm no longer having this issue.

@greenseeker
Copy link
Author

It worked for 2 days, but now getting the same error again, despite no changes to this code.

@greenseeker greenseeker reopened this May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs investigation
Projects
None yet
Development

No branches or pull requests

4 participants