# "Perform a browser refresh" doesn't warn you that it'll trash all unsaved changes

**URL:** <https://forum.inductiveautomation.com/t/perform-a-browser-refresh-doesnt-warn-you-that-itll-trash-all-unsaved-changes/24431>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [April 26, 2019, 8:57pm UTC](https://forum.inductiveautomation.com/t/perform-a-browser-refresh-doesnt-warn-you-that-itll-trash-all-unsaved-changes/24431 "2019-04-26T20:57:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![silverbacknet](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/silverbacknet/32/7385_2.png) [@silverbacknet](https://forum.inductiveautomation.com/u/silverbacknet)\
**Post date:** [April 26, 2019, 8:57pm UTC](https://forum.inductiveautomation.com/t/perform-a-browser-refresh-doesnt-warn-you-that-itll-trash-all-unsaved-changes/24431/1 "2019-04-26T20:57:57Z")

</div>

As per the title, that was very unexpected, now I have a few minutes of work to redo when I though I was finally finished. Refresh should apparently be treated just like closing the designer.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [April 29, 2019, 5:43pm UTC](https://forum.inductiveautomation.com/t/perform-a-browser-refresh-doesnt-warn-you-that-itll-trash-all-unsaved-changes/24431/2 "2019-04-29T17:43:09Z")

</div>

There’s an active PR to move that ‘refresh’ action off of the toolbar (where it’s prone to misclicks) into a shift-\>right click action on views, where it’s still accessible if you need it but unlikely to accidentally fire.