Comment 3 for bug 6

> As I just explained in report 161, I'd rather not do this --
> people would do some translations, then click the link to
> continue, and lose their work. With the navigation links at
> the top, people are unlikely to have gone through the page,
> and if they have, they're deliberately choosing to scroll
> away from "Save".

To me, this is evidence that there are two usability bugs, rather than a solution to this bug.

Bug 1: No "Next" button at the bottom of the page 2.
Bug 2: Hitting "Next" after making changes does not offer to save changes.

Obviously making the "Next" button harder to get 2 makes Bug 2 less urgent, but it doesn't solve bug 2, since a user still could hit "next" and lose their work, and it creates Bug 1 for users who scroll through the list and see no need for changes (a relatively common scenario, I'd imagine).

IMO, the best solution would be to offer the user a chance to save if they his "next" or "prev" after making changes but before saving.

Tom