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
Clicking "Save image ⇓" downloads the image but it also triggers a reload of the page. This is a problem as the page re-load does not persist the user entered data leading to total loss of work entered so far.
Immediate fix:
change the text to WARN USER they must save the json file first!
Perhaps an actual fix, seems to work when I edit the code in my browser:
Add the attribute target="_blank"
to the <a id="pngdownload" ... target="_blank"></a> element.
Possible other fix but more of a feature request:
Persist user entered data between sessions through localstorage?
The text was updated successfully, but these errors were encountered:
Clicking "Save image ⇓" downloads the image but it also triggers a reload of the page. This is a problem as the page re-load does not persist the user entered data leading to total loss of work entered so far.
Immediate fix:
change the text to WARN USER they must save the json file first!
Perhaps an actual fix, seems to work when I edit the code in my browser:
Add the attribute target="_blank"
to the <a id="pngdownload" ... target="_blank"></a> element.
Possible other fix but more of a feature request:
Persist user entered data between sessions through localstorage?
In Chrome Version 89.0.4389.128
Clicking "Save image ⇓" downloads the image but it also triggers a reload of the page. This is a problem as the page re-load does not persist the user entered data leading to total loss of work entered so far.
Immediate fix:
change the text to WARN USER they must save the json file first!
Perhaps an actual fix, seems to work when I edit the code in my browser:
Add the attribute
target="_blank"
to the
<a id="pngdownload" ... target="_blank"></a>
element.Possible other fix but more of a feature request:
Persist user entered data between sessions through localstorage?
The text was updated successfully, but these errors were encountered: