### Steps to reproduce 1. Go to page 1. 2. Navigate to page 2. 3. Click on the AwesomeBar. 4. Dismiss the keyboard. 5. Dismiss the AwesomeBar. ### Expected behaviour - The AwesomeBar is dismissed. - The browser session is still on page 2. ### Actual behaviour - The AwesomeBar is dismissed. - The browser session has navigated to page 1. ### Device information * Firefox version: n/a * Android device model: All. * Android OS version: All. ### Any additional information? * This bug does not affect Fenix or Focus because both apps have separate fragments for the AwesomeBar. It only affects browser apps that use the same fragment for both (Reference Browser).
Bug 1917496 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
### Steps to reproduce 1. Go to page 1. 2. Navigate to page 2. 3. Click on the AwesomeBar. 4. Dismiss the keyboard. 5. Dismiss the AwesomeBar. ### Expected behaviour - The AwesomeBar is dismissed. - The browser session is still on page 2. ### Actual behaviour - The AwesomeBar is dismissed. - The browser session has navigated to page 1. ### Device information * Firefox version: n/a * Android device model: All. * Android OS version: All. ### Any additional information? * This bug does not affect Fenix or Focus because both apps have separate fragments for the AwesomeBar. It only affects browser apps that use the same fragment for both (Reference Browser). * See [reference-browser#3074](https://github.com/mozilla-mobile/reference-browser/issues/3074)