canmove, Confirmed users
548
edits
Features/Jetpack/Browser-e10s-Support: Difference between revisions
Jump to navigation
Jump to search
Features/Jetpack/Browser-e10s-Support (view source)
Revision as of 20:38, 10 August 2011
, 10 August 2011no edit summary
(Created page with "{{FeatureStatus |Feature name=Browser-e10s-Support |Feature stage=Draft |Feature health=OK }} {{FeatureTeam |Feature product manager=David Mason }} {{FeaturePageBody |Feature ove...") |
No edit summary |
||
| Line 8: | Line 8: | ||
}} | }} | ||
{{FeaturePageBody | {{FeaturePageBody | ||
|Feature overview=In addition to the work we are doing to ensure that add-ons created with the Add-on SDK will run in their own processes to ensure better perfomance, there may be elements included in these add-ons which will need to run in one of the other processes, most specifically, the content process. For example, when the add-on accesses content we must ensure that is passed to the content process. This may also mean that page-mods (the modification of web pages - think "greasemonkey") will have to run in a different process than the | |Feature overview=In addition to the work we are doing to ensure that add-ons created with the Add-on SDK will run in their own processes to ensure better perfomance, there may be elements included in these add-ons which will need to run in one of the other processes, most specifically, the content process. For example, when the add-on accesses content we must ensure that is passed to the '''content process'''. This may also mean that page-mods (the modification of web pages - think "greasemonkey") will have to run in a different process than the '''add-on process'''. | ||
This continues the work to ensure that Firefox performance is optimal and supports the emerging Electrolysis work. | |||
|Feature users and use cases=As with the work to make add-ons written with the Add-on SDK run in their own process, this should work with no input from the developer at all. While we want the developer to know that this is being done for her, she need not do any extra work for the elements she's using to run in the correct processes. | |Feature users and use cases=As with the work to make add-ons written with the Add-on SDK run in their own process, this should work with no input from the developer at all. While we want the developer to know that this is being done for her, she need not do any extra work for the elements she's using to run in the correct processes. | ||
|Feature dependencies=The feature depends on platform support (specifically the Electrolysis work) for loading and executing the correct elements into the correct processes. | |Feature dependencies=The feature depends on platform support (specifically the Electrolysis work) for loading and executing the correct elements into the correct processes. | ||
}} | }} | ||
{{FeatureInfo | {{FeatureInfo | ||