You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How have you started Livebook (mix phx.server, livebook CLI, Docker, etc): Windows install
Livebook version (use git rev-parse HEAD if running with mix):
Browsers that reproduce this bug (the more the merrier): FireFox
Include what is logged in the browser console: no error
Include what is logged to the server console: no error
Current behavior
Include detailed steps to reproduce error, errors and stacktraces if appropriate.
When trying to save live book save button is grayed out.
Expected behavior
A short description on how you expect the code to behave.
open live book and try to save it in a new location.
I think I figured out the issue. The issue is a UX / UI issue not a bug.
When choosing a new DIR to save I shouldn't have to create a new live book and hit enter then save.
I should be able to save to a new location without having to create a new livebook. When clicking create new livebook you have to hit enter too, there is no button and if you click away it doesn't do anything.
Hope this makes sense.
The text was updated successfully, but these errors were encountered:
Environment
git rev-parse HEAD
if running with mix):Current behavior
Include detailed steps to reproduce error, errors and stacktraces if appropriate.
When trying to save live book save button is grayed out.
Expected behavior
A short description on how you expect the code to behave.
open live book and try to save it in a new location.
I think I figured out the issue. The issue is a UX / UI issue not a bug.
When choosing a new DIR to save I shouldn't have to create a new live book and hit enter then save.
I should be able to save to a new location without having to create a new livebook. When clicking create new livebook you have to hit enter too, there is no button and if you click away it doesn't do anything.
Hope this makes sense.
The text was updated successfully, but these errors were encountered: