|
|
| (4 intermediate revisions by one other user not shown) |
| Line 1: |
Line 1: |
| Work that is in progress:
| |
| * Developer tools (bug 937172)
| |
| * Keyboard events that are handled by both content and chrome (bug 862519)
| |
| * IME (bug 926798)
| |
| * Password manager (bug 949617)
| |
| * Alerts, prompts (bug 899648)
| |
| * Native Key bindings on OS X / Linux (bug 977904)
| |
|
| |
|
| Not yet started:
| |
| * Get software compositor in a shippable state
| |
| ** Get Talos results on par with basic layers on Linux
| |
| ** Enable on all platforms as a backup
| |
| * Better plugin support
| |
| ** Launch plugins from the parent process and share a single plugin process across content processes (bug 874016)
| |
| ** Support windowed mode plugins (bug 923746)
| |
| * Popup blocker notifications and other doorhangers (bug 933462)
| |
| * Printing (bug 927188)
| |
| * Save page as (bug 903022)
| |
| * Drag and drop (bug 936092)
| |
| * Accessibility (bug 646596)
| |
| * WebRTC UI (bug 973001)
| |
| * Click-to-play (bug 899347)
| |
| * Forward/back navigation between in-process and remote content
| |
| * Add-on installation (bug 952201)
| |
| * Focusing is sometimes broken
| |
| * Finish cross-process object wrappers
| |
| ** Bidirectional CPOWs
| |
| ** Better XPConnect integration
| |
|
| |
| * 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
| |
| ** Auto-focus on OS X
| |
| ** AeroPeek
| |
| ** Network prioritizer
| |
| ** Aero Glass with basic compositor
| |
| ** Jetpack integration
| |