176
edits
Electrolysis: Difference between revisions
→Fennec OOP-Tabs Phase II (In process)
No edit summary |
|||
| Line 63: | Line 63: | ||
Global history information. In order for link coloring to work correctly, as well as the awesomebar and other features, the content process must inform chrome when pages have been visited. The chrome process will maintain the places database and asynchronously inform the content process of the correct visited state for links. | Global history information. In order for link coloring to work correctly, as well as the awesomebar and other features, the content process must inform chrome when pages have been visited. The chrome process will maintain the places database and asynchronously inform the content process of the correct visited state for links. | ||
Proxy any other necessary profile access to the parent process. Besides what is discussed above, the content process should | Proxy any other necessary profile access to the parent process. Besides what is discussed above, the content process should have a read-only view of user preferences. | ||
Docshell-related changes. The content process maintains its view of session history. In order for back/forward to work correctly, the chrome process must have some awareness of the session history state (done). If we need to support navigating to certain about: pages (about:config), the chrome process will need to render these pages and more advanced session history will need to be developed. Links/scripts which target named or new windows (target="foo" or target="_blank") need to forward those requests to the chrome process for the Fennec UI to open a new tab (done for single content process, more work needed for multiple content processes). | Docshell-related changes. The content process maintains its view of session history. In order for back/forward to work correctly, the chrome process must have some awareness of the session history state (done). If we need to support navigating to certain about: pages (about:config), the chrome process will need to render these pages and more advanced session history will need to be developed. Links/scripts which target named or new windows (target="foo" or target="_blank") need to forward those requests to the chrome process for the Fennec UI to open a new tab (done for single content process, more work needed for multiple content processes). | ||