Bugmasters/Projects/Firefox unconfirmed

This is a list of bugs from the Firefox Desktop product, and all of them are in the "Untriaged" component. So, no one has sorted them or added enough information to know where these bugs belong. The earlier we can sort bugs, the more likely they are to be fixed. This is a net to catch bugs that didn't get triaged in their first 24 hours of life.

If you want to help Firefox users, or focus on Firefox Desktop, this is a good place to start learning. You might even see a good first bug to fix!

Force Page Refresh

Latest Untriaged Firefox bugs, UNCONFIRMED, from the last 60 days: code name, FFUNCO2mo.

You may want to edit your search, limiting it to only the operating systems you can test.

Full Query

ID	Summary	Status	Op sys	Whiteboard
2018435	Middle click fails on come links	UNCONFIRMED	Unspecified
2019987	Right-click menu does not render Copy and Paste options but empty entries	UNCONFIRMED	Unspecified
2023032	whenever i click on anything, there is a uncommon chance for it to fullscreen and turn to black	UNCONFIRMED	Unspecified
2023366	Blocage de certaines pages web avec images	UNCONFIRMED	Unspecified
2026987	depuis mise à jour firefox 115.34 0esr, disfonctionnement affichage pages	UNCONFIRMED	Unspecified
2027970	Graphical Bugs when using NoVNC in Proxmox	UNCONFIRMED	Unspecified
2029484	GP Nagpur Website: Navigation drop-down menu disappears before sub-links can be clicked.	UNCONFIRMED	Windows
2030035	https-only mode does not upgrade connections if an error code is sent back	UNCONFIRMED	Unspecified
2030086	Cache cannot be disabled	UNCONFIRMED	Unspecified
2030697	There may be a possible bug per Mozilla support chat	UNCONFIRMED	Unspecified
2030776	View Transition API: Skipped view transition due to hidden new element	UNCONFIRMED	Unspecified
2030795	Memory overflow on specific website using FF 140.9.1 (ESR)	UNCONFIRMED	Unspecified
2030807	toolkit.tabbox.switchByScrolling doesn't work with hi-res scrollwheels	UNCONFIRMED	Unspecified
2030894	browser.xul.error_pages.expert_bad_cert is no expert at all in the new felt privacy error page	UNCONFIRMED	Unspecified
2030949	Firefox sync times out for large profile	UNCONFIRMED	Unspecified
2030986	westernunion.com website crashes the whole desktop with OOM	UNCONFIRMED	Unspecified
2030993	<li><span><p></p>Introduces a gap above the text, so that it no longer aligns with the marker	UNCONFIRMED	Unspecified
2031016	Sky News ''Access Denied'' only since latest Firefox update 149.0.2	UNCONFIRMED	Unspecified
2031046	Apple Music Memory Leak on Flatpak v149.0.2	UNCONFIRMED	Linux
2031048	Firefox password sync over-write dozens of local edits	UNCONFIRMED	Unspecified

20 Total; 20 Open (100%); 0 Resolved (0%); 0 Verified (0%);

• Understand the bug
  • Read the description and comments in the bug to understand the problem.
  • If you don't understand the bug
    • Comment, add need-info flag for reporter.
    • Ask for whatever additional details you need to understand.

• Check if it's a duplicate
  • Search on similar terms in Bugzilla to see if it is a duplicate of another bug.
  • How to search for duplicate bugs: https://developer.mozilla.org/en-US/docs/Screening_duplicate_bugs
  • (How to tell if it's a likely dup)
  • Tag it dupeme? if you're not sure, and move on.
  • This search may reveal what product and component the bug should go into.

• Check if it's a support question
  • If it's a support question (often malware, FF is slow reports)
  • Nicely let the reporter know where to look for the answer or for help.
  • Ask the reporter with a need-info flag to resolve the bug as invalid, or resolve it yourself.

• Test case, if needed
  • If this bug needs a test case and you don't have one:
  • Ask the reporter for one. That might mean simplest or reduced test case code, or a URL.
  • Or you could generate a test case and attach it.

• Replicate the bug
  • Can you replicate the bug? In the same OS?
  • If you can replicated it, and no one else has, leave a comment.
  • If you can't replicate it, and are in the same OS
  • Ask the reporter with need-info if they still see the issue
    • (Especially if it's an older bug and we're on a new version of FF now)
    • If they don't you can resolve it WORKSFORME or ask reporter to do so
    • If they still see the bug, tag it needs-replication
  • If you can't replicated it and are in a different OS
    • Comment
    • tag it needs-replication

• Safe mode, plugins off, New profile
  • In some cases (but not all) you may want to ask the bug reporter if they still see the bug in safe mode (with all plugins disabled) and with a new profile.
  • (((Explain when and when perhaps not to do this)))

• IF you can replicate the bug, and it's likely to be a Firefox bug (not a bug with a plugin, etc)
  • Comment that you replicated the bug
  • Mark it NEW
  • You can keep adding info to the bug if you think it will be useful.