Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

[Bug]: BrowserLayout not loading when opening a new tab, homescreen shown instead #22316

Closed
sv-ohorvath opened this issue Nov 4, 2021 · 2 comments
Labels
🐞 bug Crashes, Something isn't working, .. eng:bug-auto-found Bug found via automated tests Feature:Browsing Issues related to browsing experience, browser navigation, not web issues S1 Blocks development/testing, may impact more than 25% of users, causes data loss, potential chemspill wontfix

Comments

@sv-ohorvath
Copy link
Contributor

sv-ohorvath commented Nov 4, 2021

*Marked as S1 because it's causing a lot of flaky tests. Please change it if it's not the appropriate label.

Steps to reproduce

Random UI tests are failing due to this, can't reproduce manually yet.
Most recent failure in visitedUrlHistoryTest - video (if you don't have access to the Firebase project, let me know )

Steps taken by the UI test:

  1. Open the app
  2. Enter an URL and press go.
  3. Wait for the page to load.

Expected behaviour

The browser loads a new tab, showing the webpage.

Actual behaviour

The page is not displayed, but a new tab is created, according to the number shown in the tab counter.

Device name

Pixel 2 (Firebase virtual device)

Android version

Android 9

Firefox release type

Firefox Nightly

Firefox version

96.0a1

Device logs

visitedUrlHistoryTest - logcat.txt

Additional information

No response

┆Issue is synchronized with this Jira Task

@sv-ohorvath sv-ohorvath added 🐞 bug Crashes, Something isn't working, .. needs:triage Issue needs triage eng:bug-auto-found Bug found via automated tests S1 Blocks development/testing, may impact more than 25% of users, causes data loss, potential chemspill labels Nov 4, 2021
@amedyne amedyne removed the needs:triage Issue needs triage label Nov 9, 2021
@sv-ohorvath
Copy link
Contributor Author

This is still affecting a lot of UI tests (see issue mentions linked).

@stale
Copy link

stale bot commented Nov 22, 2022

See: #17373 This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Nov 22, 2022
@stale stale bot closed this as completed Dec 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🐞 bug Crashes, Something isn't working, .. eng:bug-auto-found Bug found via automated tests Feature:Browsing Issues related to browsing experience, browser navigation, not web issues S1 Blocks development/testing, may impact more than 25% of users, causes data loss, potential chemspill wontfix
Projects
None yet
Development

No branches or pull requests

2 participants