For this bug, let's focus on being able to navigate back until there's no "go back" history in which case we would close the app. Take the existing example: [about:home + url1 + about:home + url2] We should be able to navigate back from about:home to url1. Currently, if we are ever on the Homepage and navigate back via a back swipe, we will close the app. Only when there's no back history should we close the app.
Bug 2026106 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
For this bug, let's focus on being able to navigate back until there's no "go back" history in which case we would close the app. We will not focus on any Forward navigation because that requires some toolbar, menu or navigation bar designs that will provide a forward button compare to the back gesture that we already have. Take the existing example: [about:home + url1 + about:home + url2] We should be able to navigate back from about:home to url1. Currently, if we are ever on the Homepage and navigate back via a back swipe, we will close the app. Only when there's no back history should we close the app.
For this bug, let's focus on being able to navigate back until there's no "go back" history in which case we would close the app. We will not focus on any Forward navigation because that requires some toolbar, menu or navigation bar designs that will provide a forward button compare to the back gesture that we already have. Take the existing example: [about:home + url1 + about:home + url2] We should be able to navigate back from about:home to url1. Currently, if we are ever on the Homepage and navigate back via a back swipe, we will close the app. Only when there's no back history should we close the app. This will be similar to Bug 2061756, but may be equivalent.