ProfessorProfessorHi, can this please be moved up in priority? It's caused a number of incidents for us now. The problem is that when we click Save on a data source, Chrome is very quick to perform the autocomplete, usually in between the time it takes your client side script to gather the data and perform the POST back. The dialog that comes up after clicking Save also gives the browser ample time to intercept with autocomplete. Even clicking between data sources without making changes now triggers the "are you sure you want move away without saving" prompt because the code detects the autocomplete as changes to the data source.
