Features/Platform/PluginsDestroyOnDisplayChange
From MozillaWiki
Please use "Edit with form" above to edit this page.
Status
| Plugins are destroyed when setting display to none | |
| Stage | Development |
| Status | In progress |
| Release target | ` |
| Health | OK |
| Status note | Bug open since 2001. |
Team
| Product manager | Chris Blizzard |
| Directly Responsible Individual | Johnny Stenback |
| Lead engineer | Josh Aas |
| 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
If you change the display of an element that contains a plugin in such a way that the plugin element gets reframed, or if you move the DOM node around in the document, then we unload the plugin and reload it. That means that any state in the plugin is lost, like say, how far into the video you were etc. This is a problem with where we represent plugins inside of Gecko and is a huge amount of work to fix.
2. Users & use cases
`
3. Dependencies
`
4. Requirements
`
Non-goals
`
Stage 2: Design
5. Functional specification
`
6. User experience design
`
Stage 3: Planning
7. Implementation plan
https://bugzilla.mozilla.org/show_bug.cgi?id=90268
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 | P2 |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | Platform |
| Secondary roadmap | ` |
| Feature list | Platform |
| Project | Flash |
| Engineering team | Plugins |
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | ` | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
