176
edits
Electrolysis: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Capncanuck (talk | contribs) mNo edit summary |
No edit summary |
||
| Line 61: | Line 61: | ||
Move all networking to the parent process. Currently the content process runs its own networking stack. Because it does not have a profile, this means that HTTPS websites don't work, cookies don't work, offline web apps don't work, etc. It also means that there is a separate memory cache for content and chrome requests. | Move all networking to the parent process. Currently the content process runs its own networking stack. Because it does not have a profile, this means that HTTPS websites don't work, cookies don't work, offline web apps don't work, etc. It also means that there is a separate memory cache for content and chrome requests. | ||
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 | 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 be have a read-only view of user preferences. | Proxy any other necessary profile access to the parent process. Besides what is discussed above, the content process should be have a read-only view of user preferences. | ||