Provide intuitive steps when Firefox can't connect
From MozillaWiki
Please use "Edit with form" above to edit this page.
Status
Provide intuitive steps when Firefox can't connect | |
Stage | Draft |
Status | ` |
Release target | ` |
Health | OK |
Status note | ` |
Team
Product manager | ` |
Directly Responsible Individual | Michael Verdi |
Lead engineer | ` |
Security lead | ` |
Privacy lead | ` |
Localization lead | ` |
Accessibility lead | ` |
QA lead | ` |
UX lead | ` |
Product marketing lead | ` |
Operations lead | ` |
Additional members | ` |
Open issues/risks
`
Stage 1: Definition
1. Feature overview
We should help people when Firefox can't connect to a website or the internet. Currently we display an error message, 3 troubleshooting tips and a "Try Again" button. Very often, especially in the case where Firefox can't connect to the internet, people are very upset that our help system is only accessible via the internet. In fact, we're adding messaging around this to the Mozilla voicemail because people often try to call us for help in this case.
After Firefox releases, often, >50% of questions relate to firewalls
What this feature would do:
- When unable to load a page, Firefox can check to see if it can still access the internet and that this isn't just a case of mistyped URL.
- If Firefox can't connect to the internet it will display a "Network Down" error page that contains a button to open a cached SUMO page with detailed steps for resolving the issue (Firefox would have to cache the SUMO page ahead of time and at regular intervals).
- The Network Down error page can serve different SUMO pages depending on conditions that it can detect. For example, if this is Windows and it's the first boot since upgrading, a SUMO article about firewalls blocking Firefox can be shown.
2. Users & use cases
- Internet Security software blocking Firefox
- Proxy errors
- DNS errors
- Problems with IPv6
- The computer is connected to a wi-fi access point that doesn't have an active internet connection
- The computer does not have an active internet connection
3. Dependencies
`
4. Requirements
`
Non-goals
`
Stage 2: Design
5. Functional specification
`
6. User experience design
`
Stage 3: Planning
7. Implementation plan
`
8. Reviews
Security review
`
Privacy review
`
Localization review
`
Accessibility
`
Quality Assurance review
`
Operations review
`
Stage 4: Development
9. Implementation
`
Stage 5: Release
10. Landing criteria
`
Feature details
Priority | Unprioritized |
Rank | 999 |
Theme / Goal | ` |
Roadmap | ` |
Secondary roadmap | ` |
Feature list | ` |
Project | ` |
Engineering team | ` |
Team status notes
status | notes | |
Products | ` | ` |
Engineering | ` | ` |
Security | ` | ` |
Privacy | ` | ` |
Localization | ` | ` |
Accessibility | ` | ` |
Quality assurance | ` | ` |
User experience | ` | ` |
Product marketing | ` | ` |
Operations | ` | ` |