I used to use a nightly build from some 2-3 months ago, and Chromium annoyed me every time I left some tabs of the ZP admin interface *without having changed, clicked or typed anything* with a popup:
http://i.imgur.com/O86riXi.png
Confirm Navigation
You have unsaved changes!
Are you sure you want to leave this page?
[Stay on this Page] [Leave this Page]

I updated to 1.4.6 today, but the same issue persists.
This appears every time I try to leave the following:
Albums > Album
Options > Gallery
Options > Image
Options > Search

Do others experience this too? Is it ZP's fault or Chromium's?

Yes, whenever you visit an admin page and change anything related to a form (like typing text and even removing it again or switching a selector), the form is "dirty" and Zenphoto warns about possible unsaved changes list if leaving.

ZP uses a third party script and it might be a problem with Chromium. Test were made using IE, Firefox, Safari and Chrome so I don't think Chromium will behave that different. you probably did accidentally change something ;-)

Maybe the administration page is a bit "dirty", but I noticed Google Chrome and especially Chromium tend to panic more often than Firefox.

For example, if I click in a field without doing any modification, Firefox usually doesn't complain, but Chrome very often does. (And I'm not talking specifically about Zenphoto, but in general.)

So this seems to be a special browser "overreaction" indeed. As the script is third party clicking on it might be considered to be a change. We use this script: https://github.com/codedance/jquery.AreYouSure/
I see there just has been an update. Maybe you could try that? The script is in `zp-core/js/`.

I'm sure I didn't react with any of the reported pages in any way.

I tested just now with the new script (simply dropping it in the old one's place and reloading the page is enough, right?) and no difference to any of the pages.

I can only assume a browser bug then. Seems to work fine for me and never bugs me (well, it does but in a good intention ;-)).

I compiled chromium-36.0.1985.49 (before that had 35.0.1916.114) but it still nags me as reported above.

When I set line 81 to false it stops nagging me, it also stops "protecting" me but that is currently preferable

`
jquery.are-you-sure.js
79 // Test on the target first as it's the most likely to be dirty
80 if (isFieldDirty($(evt.target))) {
81 setDirtyStatus($form, false);
82 return;
83 }
`

I can understand that it nags you. Still no other idea than what you did actually. But it is just a helper, best is to know yourself when you have unsaved changes :-)