Scroll back down to alias in list after updating existing alias?

[elsiehupp]

Right now, when you click the pencil icon next to an alias in the "Existing Email Aliases" list under "Mail & Users > Aliases", the page scrolls you up to the form at the top of the list to edit the alias.

It is not possible to edit an alias by entering it in the form at the top of the page; if you try to do this you will get a popover saying "Alias already exists <alias>." It would probably be preferable if there were a way to edit an existing alias from the top of the page—maybe by adding an "Edit..." button to the popover—but that's a separate issue.

After you change the "Forwards To" field an click "Update", you will get a popover saying alias updated, and then... nothing. The page does not scroll down and return you to where you started. If you want to continue from before, you need to scroll down yourself (or use in-page search).

Needless to say, this process makes a workflow involving changing multiple aliases more cumbersome than it needs to be. In the title for this Issue, I suggest automatically scrolling back to the place where the user started, but the more ideal solution would be having an in-place update form. The reason to solve the problem by automatically scrolling back down would be if scrolling to an anchor is easier to implement than the in-place form.

---

Oh, and somewhat oddly, the popovers for "Alias already exists <alias>." and alias updated use different styling, with the former including the alias in question and the latter not including the alias and additionally using monospace characters. This isn't in any way a breaking issue, but it seems like the popovers could both be changed to improve readability, to "Alias already exists." and "Alias <alias> updated.", with the alias in question possibly in monospace characters.

This is obviously also a separate issue, but I could look into it myself to begin, and I imagine it being more within my ability to fix than the others.

[elsiehupp]

Update: I've found some potential fixes, but I need to finish setting up a test environment on my computer before I can open one or more pull requests.