ericberman
commented
5 years ago I'm going to won't-fix this, for a few reasons:
- If you make an edit on the page and click this, now you need to either silently discard the change, silently accept the change, or pop-up and ask what you wanted to do. All are, IMO, bad options.
- Already have SENP. This provides redundant functionality (with the additional issue above); the only benefit is that it's above-the-fold.
- The scenario it addresses seems to be one where you're browsing around to try to find the flight you want to edit. Do people do that? And if they do, then Details view provides that functionality (as you point out) and editing from that view DOES have SENP. (There's only one edit page in the system)
- Everything added to the page has a cost, in terms of clutter, code complexity, page weight, and competition for user attention. There's already a ton of stuff on the edit flight screen; I'm really reluctant to add more for functionality that is completely duplicative.
KayRJay
It would be very handy if there were next/previous buttons or arrows ... < and > ... adjacent to the flight date on the edit screen. This would make it easy to browse flights to edit without having to scroll to the bottom of the page and use the new “Save and edit next/previous“ (“SENP”) feature.
Currently, as expected, changing the date does not navigate to a different flight, but actually changes the date for an existing flight. The feature proposed here is different: it does not change the date of a flight, but navigates to another flight in the same way as SNEP.
Rationale: Users can now save the changes made and move to an adjacent flight using SNEP. This is a natural thing to do after making changes. Using < or > adjacent to the date addresses a different use case, where the user has not / does not want to make changes in the displayed flight, but instead potentially wants to edit an “adjacent” flight.
Because the date is the first field displayed, no scrolling or extra mouse clicks would be required to move to a different flight from the Edit page without making any changes. Currently, to do this, the user has several choices. (1) He can scroll to the page bottom and use SENP, requiring a bit of scrolling. (2) He could return to the previous page using the browser BACK button. He then has to scroll to the desired flight to edit, hover and use the action list to “Edit this flight”. Four steps, clicking and scrolling. (3) If he returns to the list by pressing Logbook, the search context, list order and page position are lost, followed by even more scrolling and clicking.
It can be argued that the new < and > elements cause screen clutter, but there’s certainly space between the date and the adjacent field “Approaches”. The user convenience with < and > is worth a small bit of clutter. An alternative would be to put a summary of the flight above the data entry fields (like the one on the Details page). This takes more space, however.
It is possible currently to navigate between flights on the Details page without editing a flight. But once the user elects to edit a flight from the Details page, he must start over to move to a different flight he wants to edit.