Electrolysis/Todo: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 22: | Line 22: | ||
** Choose the right number of content processes to balance security and memory usage | ** Choose the right number of content processes to balance security and memory usage | ||
** Consider using separate content processes for iframes | ** Consider using separate content processes for iframes | ||
** about:processes page | |||
* Testing | * Testing | ||
Revision as of 08:20, 27 August 2013
- Session restore
- Developer tools
- Findbar
- Zooming
- Flash plugin
- Recursive addon events
- Form autocomplete (form history)
- Keyboard events that are handled by both content and chrome (see bug 862519)
- Drag and drop
- Accessibility and IME
- Focusing is sometimes broken
- Jetpack integration
- Get software compositor in a shippable state and enable OMTC everywhere
- Printing
- Downloads with native content type handling
- Copy-paste on Windows
- Crash reporting for content processes
- Settle on a process model
- Start with one content process for all tabs
- Measure memory usage with multiple content processes
- Choose the right number of content processes to balance security and memory usage
- Consider using separate content processes for iframes
- about:processes page
- Testing
- We expect that most tests should work without too much difficulty.
- mochitests-browser-chrome will require a lot of reworking. CPOWs may be useful here.
- Smaller issues
- Native Key bindings on OS X / Linux
- Auto-focus on OS X
- AeroPeek
- Network prioritizer
- Aero Glass with basic compositor