Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(121)

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

Issue 11035015: Merge 159156 - Extensions Docs Server: Fix headings with no IDs (Closed) Base URL: svn://svn.chromium.org/chrome/branches/1229/src/
Patch Set: Created 8 years, 2 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
OLDNEW
1 <h1>Frequently Asked Questions</h1> 1 <h1>Frequently Asked Questions</h1>
2 2
3 3
4 <!-- --> 4 <!-- -->
5 5
6 <p> 6 <p>
7 If you don't find an answer to your question here, 7 If you don't find an answer to your question here,
8 try the 8 try the
9 <a href="http://code.google.com/chrome/webstore/faq.html">Chrome Web Store FAQ</ a>, the 9 <a href="http://code.google.com/chrome/webstore/faq.html">Chrome Web Store FAQ</ a>, the
10 <a href="http://stackoverflow.com/questions/tagged/google-chrome-extension">[goo gle-chrome-extension] tag on Stack Overflow</a>, the 10 <a href="http://stackoverflow.com/questions/tagged/google-chrome-extension">[goo gle-chrome-extension] tag on Stack Overflow</a>, the
11 <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions">grou p</a>, or the 11 <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions">grou p</a>, or the
12 <a href="http://www.google.com/support/chrome_webstore/">store help</a>. 12 <a href="http://www.google.com/support/chrome_webstore/">store help</a>.
13 </p> 13 </p>
14 14
15 <div id="faq-TOC"> 15 <div id="faq-TOC">
16 <h4>General</h4> 16 <h4 id="general">General</h4>
17 <ul> 17 <ul>
18 <li><a href="#faq-gen-01">What are Google Chrome Extensions?</a></li> 18 <li><a href="#faq-gen-01">What are Google Chrome Extensions?</a></li>
19 <li><a href="#faq-dev-01">How can I set up Chrome for extension development? </a></li> 19 <li><a href="#faq-dev-01">How can I set up Chrome for extension development? </a></li>
20 <li><a href="#faq-gen-02">What technologies are used to write extensions for Chrome?</a></li> 20 <li><a href="#faq-gen-02">What technologies are used to write extensions for Chrome?</a></li>
21 <li><a href="#faq-gen-03">Are extensions fetched from the web every time the browser is loaded?</a></li> 21 <li><a href="#faq-gen-03">Are extensions fetched from the web every time the browser is loaded?</a></li>
22 <li><a href="#faq-dev-14">How do I determine which version of Chrome is depl oyed to which channel?</a></li> 22 <li><a href="#faq-dev-14">How do I determine which version of Chrome is depl oyed to which channel?</a></li>
23 </ul> 23 </ul>
24 <h4>Capabilities</h4> 24 <h4 id="capabilities">Capabilities</h4>
25 <ul> 25 <ul>
26 <li><a href="#faq-dev-02">Can extensions make cross-domain Ajax requests?</a ></li> 26 <li><a href="#faq-dev-02">Can extensions make cross-domain Ajax requests?</a ></li>
27 <li><a href="#faq-dev-03">Can extensions use 3rd party web services?</a></li > 27 <li><a href="#faq-dev-03">Can extensions use 3rd party web services?</a></li >
28 <li><a href="#faq-dev-07">Can extensions encode/decode JSON data?</a></li> 28 <li><a href="#faq-dev-07">Can extensions encode/decode JSON data?</a></li>
29 <li><a href="#faq-dev-08">Can extensions store data locally?</a></li> 29 <li><a href="#faq-dev-08">Can extensions store data locally?</a></li>
30 <li><a href="#faq-dev-04">Can extensions use OAuth?</a></li> 30 <li><a href="#faq-dev-04">Can extensions use OAuth?</a></li>
31 <li><a href="#faq-dev-06">Can extensions load DLLs?</a></li> 31 <li><a href="#faq-dev-06">Can extensions load DLLs?</a></li>
32 <li><a href="#faq-dev-05">Can extensions create UI outside of the rendered w eb page?</a></li> 32 <li><a href="#faq-dev-05">Can extensions create UI outside of the rendered w eb page?</a></li>
33 <li><a href="#faq-interact-chrome">Can extensions listen to clicks on Chrome tabs and navigation buttons?</a> 33 <li><a href="#faq-interact-chrome">Can extensions listen to clicks on Chrome tabs and navigation buttons?</a>
34 <li><a href="#faq-dev-11">Can two extensions communicate with each other?</a ></li> 34 <li><a href="#faq-dev-11">Can two extensions communicate with each other?</a ></li>
35 <li><a href="#faq-dev-13">Can extensions use Google Analytics?</a></li> 35 <li><a href="#faq-dev-13">Can extensions use Google Analytics?</a></li>
36 <li><a href="#faq-dev-15">Can extensions modify chrome:// URLs?</a></li> 36 <li><a href="#faq-dev-15">Can extensions modify chrome:// URLs?</a></li>
37 <li><a href="#faq-open-popups">Can extensions open browser/page action popup s without user interaction?</a></li> 37 <li><a href="#faq-open-popups">Can extensions open browser/page action popup s without user interaction?</a></li>
38 <li><a href="#faq-persist-popups">Can extensions keep popups open after the user clicks away from them?</a></li> 38 <li><a href="#faq-persist-popups">Can extensions keep popups open after the user clicks away from them?</a></li>
39 <li><a href="#faq-lifecycle-events">Can extensions be notified when they are installed/uninstalled?</a></li> 39 <li><a href="#faq-lifecycle-events">Can extensions be notified when they are installed/uninstalled?</a></li>
40 </ul> 40 </ul>
41 <h4>Development</h4> 41 <h4 id="development">Development</h4>
42 <ul> 42 <ul>
43 <li><a href="#faq-building-ui">How do I build a UI for my extension?</a> 43 <li><a href="#faq-building-ui">How do I build a UI for my extension?</a>
44 <li><a href="#faq-dev-09">How much data can I store in localStorage?</a></li > 44 <li><a href="#faq-dev-09">How much data can I store in localStorage?</a></li >
45 <li><a href="#faq-dev-10">How do I create an options menu for my application ?</a></li> 45 <li><a href="#faq-dev-10">How do I create an options menu for my application ?</a></li>
46 <li><a href="#faq-dev-12">What debugging tools are available to extension de velopers?</a></li> 46 <li><a href="#faq-dev-12">What debugging tools are available to extension de velopers?</a></li>
47 <li><a href="#faq-dev-16">Why do wildcard matches not work for top level dom ains (TLDs)?</a></li> 47 <li><a href="#faq-dev-16">Why do wildcard matches not work for top level dom ains (TLDs)?</a></li>
48 <li><a href="#faq-management">Why does the management API not fire events wh en my extension is installed/uninstalled?</a></li> 48 <li><a href="#faq-management">Why does the management API not fire events wh en my extension is installed/uninstalled?</a></li>
49 <li><a href="#faq-firstrun">How can an extension determine whether it is run ning for the first time?</a></li> 49 <li><a href="#faq-firstrun">How can an extension determine whether it is run ning for the first time?</a></li>
50 </ul> 50 </ul>
51 <h4>Features and bugs</h4> 51 <h4 id="features">Features and bugs</h4>
52 <ul> 52 <ul>
53 <li><a href="#faq-fea-01">I think I've found a bug! How do I make sure it ge ts fixed?</a></li> 53 <li><a href="#faq-fea-01">I think I've found a bug! How do I make sure it ge ts fixed?</a></li>
54 <li><a href="#faq-fea-02">I have a feature request! How can I report it?</a> </li> 54 <li><a href="#faq-fea-02">I have a feature request! How can I report it?</a> </li>
55 </ul> 55 </ul>
56 </div> 56 </div>
57 57
58 <h2>General</h2> 58 <h2 id="general2">General</h2>
59 59
60 <h3 id="faq-gen-01">What are Google Chrome Extensions?</h3> 60 <h3 id="faq-gen-01">What are Google Chrome Extensions?</h3>
61 <p> 61 <p>
62 Google Chrome Extensions are applications that run inside the 62 Google Chrome Extensions are applications that run inside the
63 Chrome browser and provide additional functionality, integration with third 63 Chrome browser and provide additional functionality, integration with third
64 party websites or services, and customized browsing experiences. 64 party websites or services, and customized browsing experiences.
65 </p> 65 </p>
66 66
67 <h3 id="faq-dev-01">How can I set up Chrome for extension development?</h3> 67 <h3 id="faq-dev-01">How can I set up Chrome for extension development?</h3>
68 <p> 68 <p>
(...skipping 73 matching lines...) Expand 10 before | Expand all | Expand 10 after
142 <code>cros</code> (Google Chrome OS). The listed 142 <code>cros</code> (Google Chrome OS). The listed
143 channels are <code>canary</code>, <code>dev</code>, <code>beta</code>, 143 channels are <code>canary</code>, <code>dev</code>, <code>beta</code>,
144 and <code>stable</code>. 144 and <code>stable</code>.
145 The two four-part numbers after the channel represent the current and previous 145 The two four-part numbers after the channel represent the current and previous
146 versions of Chrome deployed to that platform-channel 146 versions of Chrome deployed to that platform-channel
147 combination. The rest of the information is metadata about when the releases 147 combination. The rest of the information is metadata about when the releases
148 were first pushed, as well as revision numbers associated with each build. 148 were first pushed, as well as revision numbers associated with each build.
149 </p> 149 </p>
150 150
151 151
152 <h2>Capabilities</h2> 152 <h2 id="capabilities2">Capabilities</h2>
153 153
154 <h3 id="faq-dev-02">Can extensions make cross-domain Ajax requests?</h3> 154 <h3 id="faq-dev-02">Can extensions make cross-domain Ajax requests?</h3>
155 <p> 155 <p>
156 Yes. Extensions can make cross-domain requests. See 156 Yes. Extensions can make cross-domain requests. See
157 <a href="http://code.google.com/chrome/extensions/xhr.html">this page</a> 157 <a href="http://code.google.com/chrome/extensions/xhr.html">this page</a>
158 for more information. 158 for more information.
159 </p> 159 </p>
160 160
161 <h3 id="faq-dev-03">Can extensions use 3rd party web services?</h3> 161 <h3 id="faq-dev-03">Can extensions use 3rd party web services?</h3>
162 <p> 162 <p>
(...skipping 112 matching lines...) Expand 10 before | Expand all | Expand 10 after
275 <h3 id="faq-lifecycle-events">Can extensions be notified when they are 275 <h3 id="faq-lifecycle-events">Can extensions be notified when they are
276 installed/uninstalled?</h3> 276 installed/uninstalled?</h3>
277 <p> 277 <p>
278 No, there are no events an extension can listen to in order to determine 278 No, there are no events an extension can listen to in order to determine
279 whether it has been installed or uninstalled. However, an extension can 279 whether it has been installed or uninstalled. However, an extension can
280 determine when it has been run for the first time. See <a 280 determine when it has been run for the first time. See <a
281 href="#faq-firstrun">this FAQ entry</a> for information. 281 href="#faq-firstrun">this FAQ entry</a> for information.
282 </p> 282 </p>
283 283
284 284
285 <h2>Development</h2> 285 <h2 id="development2">Development</h2>
286 286
287 287
288 <h3 id="faq-building-ui">How do I build a UI for my extension?</h3> 288 <h3 id="faq-building-ui">How do I build a UI for my extension?</h3>
289 <p> 289 <p>
290 Extensions use HTML and CSS to define their user interfaces, so you can use 290 Extensions use HTML and CSS to define their user interfaces, so you can use
291 standard form controls to build your UI, or style the interface with CSS, 291 standard form controls to build your UI, or style the interface with CSS,
292 as you would a web page. Additionally, extensions can add 292 as you would a web page. Additionally, extensions can add
293 <a href="#faq-dev-05">some limited UI elements to Chrome itself.</a> 293 <a href="#faq-dev-05">some limited UI elements to Chrome itself.</a>
294 </p> 294 </p>
295 295
(...skipping 62 matching lines...) Expand 10 before | Expand all | Expand 10 after
358 358
359 <pre>var firstRun = (localStorage['firstRun'] == 'true'); 359 <pre>var firstRun = (localStorage['firstRun'] == 'true');
360 if (!firstRun) { 360 if (!firstRun) {
361 localStorage['firstRun'] = 'true'; 361 localStorage['firstRun'] = 'true';
362 }</pre> 362 }</pre>
363 363
364 <p> 364 <p>
365 Note that this check should be run in a background page, not a content script. 365 Note that this check should be run in a background page, not a content script.
366 </p> 366 </p>
367 367
368 368 <h2 id="features2">Features and bugs</h2>
369 <h2>Features and bugs</h2>
370 369
371 370
372 <h3 id="faq-fea-01">I think I've found a bug! How do I make sure it gets 371 <h3 id="faq-fea-01">I think I've found a bug! How do I make sure it gets
373 fixed?</h3> 372 fixed?</h3>
374 <p> 373 <p>
375 While developing an extension, you may find behavior that does not 374 While developing an extension, you may find behavior that does not
376 match the extensions documentation and may be the result of a bug in 375 match the extensions documentation and may be the result of a bug in
377 Chrome. The best thing to do is to make sure an appropriate issue 376 Chrome. The best thing to do is to make sure an appropriate issue
378 report is filed, and the Chromium team has enough information to reproduce 377 report is filed, and the Chromium team has enough information to reproduce
379 the behavior. 378 the behavior.
(...skipping 96 matching lines...) Expand 10 before | Expand all | Expand 10 after
476 ticket has not been modified after two weeks, please post a message to the 475 ticket has not been modified after two weeks, please post a message to the
477 <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions/t opics"> 476 <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions/t opics">
478 discussion group</a> with a link back to your request. 477 discussion group</a> with a link back to your request.
479 </li> 478 </li>
480 <li> 479 <li>
481 If you originally reported your request on the discussion group and were 480 If you originally reported your request on the discussion group and were
482 directed to this FAQ entry, reply to your original thread with a link 481 directed to this FAQ entry, reply to your original thread with a link
483 to the ticket you starred or opened. This will make it easier for others 482 to the ticket you starred or opened. This will make it easier for others
484 with the same request to find the correct ticket. 483 with the same request to find the correct ticket.
485 </li> 484 </li>
486 </ol> 485 </ol>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698