{"json_modified": "2016-03-28T08:31:13.711085", "uuid": "0a5c152e-3f64-44e0-895f-3df8744d5e4d", "title": "Content Processes", "url": "/en-US/docs/Mozilla/Add-ons/SDK/Guides/Contributor_s_Guide/Content_Processes", "tags": ["Add-on SDK"], "translations": [], "modified": "2016-01-15T09:51:59", "label": "Content Processes", "localization_tags": [], "locale": "en-US", "id": 86029, "last_edit": "2016-01-15T09:51:57", "summary": "A content process was supposed to run all the code associated with a single tab. Conversely, an add-on process was supposed to run all the code associated with a single add-on. Neither content or add-on proceses were ever actually implemented, but by the time they were cancelled, the SDK was already designed with them in mind. To understand this article, it's probably best to read it as if content and add-on processes actually exist.", "sections": [{"id": "Quick_Links", "title": null}, {"id": "Content_Scripts", "title": "Content Scripts"}, {"id": "Event_Emitters", "title": "Event Emitters"}, {"id": "Content_Workers", "title": "Content Workers"}, {"id": "Accessing_the_DOM", "title": "Accessing the DOM"}, {"id": "A_few_Notes_on_Security", "title": "A few Notes on Security"}], "slug": "Mozilla/Add-ons/SDK/Guides/Contributor_s_Guide/Content_Processes", "review_tags": []}