chrome/common/extensions/docs/templates/articles/app_architecture.html - Issue 291663002: Adjustments to the fatnav and sidenav, and other CSS updates

Side by Side Diff: chrome/common/extensions/docs/templates/articles/app_architecture.html

Issue 291663002: Adjustments to the fatnav and sidenav, and other CSS updates (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: Added missing copyright license. Fixed bad indentation on search.js Created 6 years, 6 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

« no previous file with comments | « chrome/common/extensions/docs/templates/articles/api_index.html ('k') | chrome/common/extensions/docs/templates/articles/content_scripts.html » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
1 <meta name="doc-family" content="apps">	1 <meta name="doc-family" content="apps">

2 <h1>Chrome Apps Architecture</h1>	2 <h1>Chrome Apps Architecture</h1>

3	3

4	4

5 <p>	5 <p>

6 Chrome Apps integrate closely with a user’s operating system.	6 Chrome Apps integrate closely with a user’s operating system.

7 They are designed to be run outside of a browser tab,	7 They are designed to be run outside of a browser tab,

8 to run robustly in offline and poor connectivity scenarios and	8 to run robustly in offline and poor connectivity scenarios and

9 to have far more powerful capabilities than are available	9 to have far more powerful capabilities than are available

10 in a typical web browsing environment.	10 in a typical web browsing environment.

(...skipping 48 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
59 <p>	59 <p>

60 The “event page” manages the Chrome App lifecycle	60 The “event page” manages the Chrome App lifecycle

61 by responding to user gestures and system events.	61 by responding to user gestures and system events.

62 This page is invisible, only exists in the background,	62 This page is invisible, only exists in the background,

63 and can be closed automatically by the system runtime.	63 and can be closed automatically by the system runtime.

64 It controls how windows open and close and	64 It controls how windows open and close and

65 when the app is started or terminated.	65 when the app is started or terminated.

66 There can only be one “event page” for a Chrome App.	66 There can only be one “event page” for a Chrome App.

67 <p>	67 <p>

68	68

69 <p>	69 <div class="video-container">

70 <iframe title="YouTube video player" width="610" height="380" src="//www.youtube .com/embed/yr1jgREbH8U" frameborder="0" allowfullscreen></iframe>	70 <iframe title="YouTube video player" width="610" height="380" src="//www.youtu be.com/embed/yr1jgREbH8U" frameborder="0" allowfullscreen></iframe>

71 </p>	71 </div>

72	72

73 <h3 id="lifecycle">App lifecycle at a glance</h3>	73 <h3 id="lifecycle">App lifecycle at a glance</h3>

74	74

75 <p>	75 <p>

76 For detailed instructions on how to use the programming model,	76 For detailed instructions on how to use the programming model,

77 see <a href="app_lifecycle">Manage App Lifecycle</a>.	77 see <a href="app_lifecycle">Manage App Lifecycle</a>.

78 Here's a brief summary of the Chrome App lifecyle	78 Here's a brief summary of the Chrome App lifecyle

79 to get you started:	79 to get you started:

80 </p>	80 </p>

81	81

(...skipping 77 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
159 and can’t access the storage of another app	159 and can’t access the storage of another app

160 or personal data (such as cookies) for websites that you use in your browser.	160 or personal data (such as cookies) for websites that you use in your browser.

161 All external processes are isolated from the app.	161 All external processes are isolated from the app.

162 Since iframes run in the same process as the surrounding page,	162 Since iframes run in the same process as the surrounding page,

163 they can only be used to load other app pages.	163 they can only be used to load other app pages.

164 You can use the <code>object</code> tag to	164 You can use the <code>object</code> tag to

165 <a href="app_external">embed external content</a>;	165 <a href="app_external">embed external content</a>;

166 this content runs in a separate process from the app.	166 this content runs in a separate process from the app.

167 </p>	167 </p>

168	168

169 <p>	169 <div class="video-container">

170 <iframe title="YouTube video player" width="610" height="380" src="//www.youtube .com/embed/EDtiWN42lHs" frameborder="0" allowfullscreen></iframe>	170 <iframe title="YouTube video player" width="610" height="380" src="//www.youtu be.com/embed/EDtiWN42lHs" frameborder="0" allowfullscreen></iframe>

171 </p>	171 </div>

172

173 <p class="backtotop"><a href="#top">Back to top</a></p>

OLD	NEW