This is fixed for 2.0.2, though not in the recommended way. I looked at applying autocomplete in a few places, though there are minor disadvantages with that. Primarily, it has to do with back and forward buttons and retaining the cached value which we'd want to do.
This is generally only significant when we redirect back to the same URL after saving. In this case, we were calling window.location.reload()
in JS. This takes an argument over whether the reload is forced -- setting that to true resolves this issue.