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
When changing anything in the user preferences, Chromium browsers will always complain that the page is "dirty".
How to reproduce
Go to a Statamic site using a Chromium browser such as Chrome, Edge, or Arc. This can even be a newly installed vanilla Statamic site.
Log into the CP
Go to the User > Preferences page
Pick or change your Locale
Click Save
The expected behavior is that the preferences are saved with no warnings from the browser. This is, in fact, what happens when using Safari on a Mac.
The actual result is that the preferences are saved, but the Chromium browser issues a warning alert "Changes you made may not be saved." and forces you to choose between "OK" and "Cancel", both of which sounds since you want the changes saved. The good news is that the changes were saved. The bad news is that this is a very annoying and confusing warning.
Possibly related, when using Bard fields similar "dirty" state confusion often arises in Chromium browsers. Virtually every page I have with a Bard field with complex sets ends up exhibiting similar behavior. Lots of spurious "dirty" alerts, most of which are mistaken. This reduces the impact of these alerts, making our users inclined to click "OK" without really considering the message. A dangerous state of affairs.
The text was updated successfully, but these errors were encountered:
Bug description
When changing anything in the user preferences, Chromium browsers will always complain that the page is "dirty".
How to reproduce
The expected behavior is that the preferences are saved with no warnings from the browser. This is, in fact, what happens when using Safari on a Mac.
The actual result is that the preferences are saved, but the Chromium browser issues a warning alert "Changes you made may not be saved." and forces you to choose between "OK" and "Cancel", both of which sounds since you want the changes saved. The good news is that the changes were saved. The bad news is that this is a very annoying and confusing warning.
Logs
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
Possibly related, when using Bard fields similar "dirty" state confusion often arises in Chromium browsers. Virtually every page I have with a Bard field with complex sets ends up exhibiting similar behavior. Lots of spurious "dirty" alerts, most of which are mistaken. This reduces the impact of these alerts, making our users inclined to click "OK" without really considering the message. A dangerous state of affairs.
The text was updated successfully, but these errors were encountered: