Features/Firefox/Windows Plugin Hang UI

Please use "Edit with form" above to edit this page.

Status

Windows Plugin Hang UI
Stage	Planning
Status	`
Release target	Firefox 19
Health	OK
Status note	`

{{#set:Feature name=Windows Plugin Hang UI

|Feature stage=Planning |Feature status=` |Feature version=Firefox 19 |Feature health=OK |Feature status note=` }}

Team

Product manager	asa
Directly Responsible Individual	bsmedberg
Lead engineer	`
Security lead	`
Privacy lead	`
Localization lead	`
Accessibility lead	`
QA lead	Manuela Muntean
UX lead	`
Product marketing lead	`
Operations lead	`
Additional members	`

{{#set:Feature product manager=asa

|Feature feature manager=bsmedberg |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=Manuela Muntean |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature 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

` {{#set:Feature open issues and risks=` |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. |Feature users and use cases=` |Feature dependencies=` |Feature requirements=` |Feature non-goals=This project is currently scoped to Windows only. |Feature functional spec=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. |Feature ux design=` |Feature 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. |Feature security review=` |Feature privacy review=` |Feature localization review=The native win32 app will need to have a few localized strings: we don't need to compile these in. |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature 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

{{#set:Feature priority=Unprioritized

|Feature rank=999 |Feature theme=` |Feature roadmap=Plugin Interactions |Feature secondary roadmap=Firefox Desktop |Feature list=Desktop |Feature project=Flash |Feature engineering team=Plugins }}

Team status notes

	status	notes
Products	`	`
Engineering	`	`
Security	`	`
Privacy	`	`
Localization	`	`
Accessibility	`	`
Quality assurance	`	Plugin Hang UI/TestPlan Test Plan
User experience	`	`
Product marketing	`	`
Operations	`	`

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=Plugin Hang UI/TestPlan Test Plan |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}