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

@bind inside table always renders in "Safe Preview" mode #2994

Closed
dpgarrick opened this issue Aug 13, 2024 · 3 comments
Closed

@bind inside table always renders in "Safe Preview" mode #2994

dpgarrick opened this issue Aug 13, 2024 · 3 comments

Comments

@dpgarrick
Copy link

dpgarrick commented Aug 13, 2024

Tiny reproduction is here:

https://gist.github.com/dpgarrick/9dccbeb1a09821402e2e27e385a2f2fc

Even after running the notebook code and disabling safe preview, the warning message still appears, and the field itself is unusable/uneditable - any changes the user makes to that value in the NumberField element does not save or propagate.

I had a go with Claude AI to try and diagnose and fix the issue in the Pluto code but was unsuccessful....React is not my thing.

The fix (maybe) is for the bonded elements to be regenerated once the safe preview is disabled, otherwise they are stuck in a disabled "safe preview" mode forever.

Unclear to me if this is a Pluto.jl or PlutoUI.jl bug given the safe preview logic is handled here, but it is not propagating to a PlutoUI element. Seems like it is a Pluto.jl issue but if actually the latter then this issue can be moved to that repo.

@fonsp
Copy link
Owner

fonsp commented Aug 14, 2024

Hey @dpgarrick ! Could you post a screenshot?

@dpgarrick
Copy link
Author

Sure!

Before running
image

After running
image

And adjusting the myField values doesn't propagate.

@fonsp fonsp changed the title bonded UI fields never exit safe preview mode @bind inside table always renders in "Safe Preview" mode Aug 15, 2024
@fonsp fonsp closed this as completed in 1162af4 Aug 15, 2024
@fonsp
Copy link
Owner

fonsp commented Aug 15, 2024

Thanks! fixed in the next release

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

No branches or pull requests

2 participants