Maps reordered wrong on load and cannot rearrange them

When I load my campaign and click the pages icon to view the listing of all of my maps, I find the ordering to be not how I left it and upon trying to drag and drop to reorder them, they snap back to how they were before. I found if I add a new page, I am able to reorder the maps successfully, however if I then delete it and load a map it goes back to the wrong ordering (and again refuses to reorder). Practical example: I have 21 active maps currently and they are arranged in a very specific order to make it easy to jump between them during my next session (20 of the 21 are expected to be used in the next session, the last one is a blank grid I use whenever I don't have any maps drawn for a particular area beforehand -- I split them up into 20 maps to reduce load times for my players as all of them are quite large). No errors are produced in the console when I try to rearrange the maps, they just snap back to where they were before (there are some debug messages there but nothing seemed out of the ordinary). Browser/OS info: Google Chrome 35.0.1897.2 dev-m on Windows 7.

Are you having this same issue in all your campaigns or just one? Also, did you try following all of the steps on the troubleshooting guide ? We've had some really strange behaviors caused by extensions and things lingering in the browser cache before. I'd like to rule that out as a possibility.

I only have the one campaign. It appears to work just fine in Firefox, however it was still happening on Chrome even after clearing the cache and viewing it in Incognito with every extension disabled. From that, I think the issue is with a change recently made in Chrome (since I'm running on the dev channel). It could either be a bug with the dev channel (not game-breaking in that case, since usually I have far less maps active at a time, so rearranging them isn't a huge deal -- all maps are still accessible) or some API change for the newer versions that broke compatibility with stuff. If I remember and it gets fixed in a later chrome update, I'll post back here.