The "Previous" button at the bottom of the screen navigates you back through the breadcrumb bar components at the top. While it's fine to have a "Previous" button at the bottom, there should also be one at the top, near the "map" (the breadcrumb bar) being navigated. On a tall page, the breadcrumb trail will be off-screen when one is scrolled to the bottom, so if one is forced to scroll to the bottom in order to get to the "Previous" button, one loses sight of one's map -- not a good UX.
Now, it might be that once issue #1048 is fixed, and assuming we make sure the browser's native Back button works everywhere, we don't even need a Previous button at all. Getting rid of it would be a fine way to close this issue -- but while we have it, we should have it where it's needed.
Now scroll to the bottom, where "Previous" button is, and lose sight of the top breadcrumb bar:
The "Previous" button at the bottom of the screen navigates you back through the breadcrumb bar components at the top. While it's fine to have a "Previous" button at the bottom, there should also be one at the top, near the "map" (the breadcrumb bar) being navigated. On a tall page, the breadcrumb trail will be off-screen when one is scrolled to the bottom, so if one is forced to scroll to the bottom in order to get to the "Previous" button, one loses sight of one's map -- not a good UX.
Now, it might be that once issue #1048 is fixed, and assuming we make sure the browser's native Back button works everywhere, we don't even need a Previous button at all. Getting rid of it would be a fine way to close this issue -- but while we have it, we should have it where it's needed.
Now scroll to the bottom, where "Previous" button is, and lose sight of the top breadcrumb bar: