Skip to content

Bug 1557154: Describe supported browsers in the User Guide - #195

Open
topunix wants to merge 1 commit into
bugzilla:mainfrom
topunix:bug-1557154
Open

topunix wants to merge 1 commit into
bugzilla:mainfrom
topunix:bug-1557154

Conversation

@topunix

@topunix topunix commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

Fixes https://bugzilla.mozilla.org/show_bug.cgi?id=1557154

Adds a Supported Browsers page to the User Guide (docs/en/rst/using/browser-support.rst) and links it from the User Guide index.

The tiers are adapted from the existing browser support policy on the BMO wiki (https://wiki.mozilla.org/BMO#Browser_Support_For_BMO), made generic for upstream:

  • Full support: current Firefox (including the latest ESR), current Chrome and other Chromium-based browsers such as Edge, current Safari
  • Limited support: the previous release of each, the previous Firefox ESR, and pre-release builds
  • Not supported: Internet Explorer
  • JavaScript required for full functionality

Firefox ESR stays in full support since bug 1557596 (dropping ESR) was resolved WONTFIX. The BMO-specific analytics and Do Not Track notes were left out. Happy to adjust the tiers if the project wants a different policy for 6.0.

Built locally with Sphinx; the new page renders and adds no warnings.

Add a Supported Browsers page to the User Guide, adapted from the browser support policy on the BMO wiki: full support for current Firefox (including the latest ESR), Chromium-based browsers and Safari; limited support for the previous release of each and for pre-release builds; Internet Explorer unsupported; JavaScript required for full functionality.

@mrenvoize mrenvoize left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving. It's a docs-only change, so there's no regression risk. I checked that the new page parses cleanly with docutils, that its heading style matches the sibling pages, and that nothing else in the docs states a conflicting browser policy.

One wording suggestion, which is not blocking. The opening line says Bugzilla is "developed and tested against current desktop web browsers". The project's automated browser tests use Firefox only (TWD_BROWSER=firefox against selenium/standalone-firefox in all three docker-compose.test-*.yml files). Chrome, Edge and Safari are expected to work, but they aren't tested. Something like "Bugzilla is tested with Firefox. Other current desktop browsers are expected to work" would be more accurate, and it avoids promising test coverage that doesn't exist.

Two small nits:

  • browser-support sits between "Creating an Account" and "Filing a Bug" in the User Guide index. It probably belongs at the end of the list.
  • The tiers are adapted from the BMO wiki policy, as the description says.

@justdave

justdave commented Nov 9, 2026

Copy link
Copy Markdown
Member

Since this is documentation-only, I'm happy to merge this immediately, even through we're in release-freeze for the 5.2.1 release cohort right now, though Martin's test-coverage nit probably ought to be addressed before we merge it.

@justdave

justdave commented Nov 9, 2026

Copy link
Copy Markdown
Member

Long term, getting our tests to test with other browsers as well would be cool, but that's out of scope for this PR.

@justdave

justdave commented Nov 9, 2026

Copy link
Copy Markdown
Member

And just to make it clear, we do support the other major browsers in the terms that if something is broken on that browser it would be considered a bug and we would fix it, we just aren't actively testing those right now.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants