Features/Firefox/Windows Plugin Hang UI
Status
| Windows Plugin Hang UI | |
| Stage | Planning |
| Status | ` |
| Release target | Firefox 19 |
| Health | OK |
| Status note | ` |
Team
| Product manager | asa |
| Directly Responsible Individual | bsmedberg |
| Lead engineer | Aaron Klotz |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | Manuela Muntean |
| UX lead | ` |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
Open issues/risks
`
Stage 1: Definition
1. Feature overview
Currently when the Flash plugin stops responding, Firefox also stops responding. Firefox waits a preset amount of time (45 seconds) and then kills the plugin. During this time Firefox appears to be locked and doesn't respond.
This feature will improve the user experience of a plugin not responding by showing UI which allows the user to see that it is the plugin (not Firefox) which is broken, and allowing the user to kill the plugin right away if they don't want to wait.
2. Users & use cases
`
3. Dependencies
`
4. Requirements
`
Non-goals
This project is currently scoped to Windows only.
Stage 2: Design
5. Functional specification
When a plugin stops responding for a short amount of time (5 seconds?) we will overlay the normal browser UI with a dialog which shows which plugin is not responding and allows the user to kill that plugin.
We will continue to automatically kill plugins after a longer timeout, the current 45 seconds or even longer to 60 seconds.
6. User experience design
`
Stage 3: Planning
7. Implementation plan
We cannot effectively show UI in the Firefox process because the main thread is hung and spinning a nested event loop will cause problems. So it will be necessary to have a separate win32 app which communicates with Firefox and shows the UI.
8. Reviews
Security review
`
Privacy review
`
Localization review
The native win32 app will need to have a few localized strings: we don't need to compile these in.
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 | Plugin Interactions |
| Secondary roadmap | Firefox Desktop |
| Feature list | Desktop |
| Project | Flash |
| Engineering team | Plugins |
Team status notes
| status | notes | |||||||||
| Products | ` | ` | ||||||||
| Engineering | ` |
1 Total; 0 Open (0%); 1 Resolved (100%); 0 Verified (0%); |
||||||||
| Security | sec-review-needed |
1 Total; 1 Open (100%); 0 Resolved (0%); 0 Verified (0%); |
||||||||
| Privacy | ` | ` | ||||||||
| Localization | ` | ` | ||||||||
| Accessibility | ` | ` | ||||||||
| Quality assurance | ` | Test Plan | ||||||||
| User experience | ` | ` | ||||||||
| Product marketing | ` | ` | ||||||||
| Operations | ` | ` |
- The given value "
Full Query ID Summary Priority Status 805591 Add UI to be shown when plugin is unresponsive -- RESOLVED 1 Total; 0 Open (0%); 1 Resolved (100%); 0 Verified (0%);
" contains strip markers and therefore it cannot be parsed sufficiently. - The given value "
Full Query ID Summary Priority Status 801806 SecReview: Windows Plugin Hang UI -- NEW 1 Total; 1 Open (100%); 0 Resolved (0%); 0 Verified (0%);
" contains strip markers and therefore it cannot be parsed sufficiently.
