Split from bug 166588 back button: while each tab allows to move forward via the "Next" button, there is no "Back" button. Tabs can be navigated by the top, but again, if there is a "Next" button, users will also expect a "Back" button. The logic goes both ways. See attachment 200824 [details]
I don't think this is needed. This kind of over-engineering rather harms UX. => WF
(In reply to Heiko Tietze from comment #1) > I don't think this is needed. This kind of over-engineering rather harms UX. If you have a "Next" button, and that's not over-engineering, then you need a "Previous" or "Back" button. Dialogs with Prev/Next button control for movement between tabs are a common and well-established UI idiom; so are dialogs with no Prev and no Next, just tabs. But one direction without the other? That's rare, and I was definitely missing the button. You could, in principle, drop the Next entirely, and just have a Close/Dismiss button; but that would discourage people from moving forward beyond the "Welcome" tab.
The Next button was suggested as a trigger to go through the dialog.
(In reply to Heiko Tietze from comment #3) > The Next button was suggested as a trigger to go through the dialog. And rightly so! ... but the buttons go together. Like in installer dialogs.
"... but the buttons go together. Like in installer dialogs." 👈 this. As stated in the initial report.