OLD | NEW |
---|---|
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 |
(...skipping 59 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
70 extensions, you already have everything you need to start writing an | 70 extensions, you already have everything you need to start writing an |
71 extension of your own. | 71 extension of your own. |
72 You can start by turning on Developer mode. | 72 You can start by turning on Developer mode. |
73 </p> | 73 </p> |
74 | 74 |
75 <p> | 75 <p> |
76 Click the Chrome menu icon | 76 Click the Chrome menu icon |
77 <img src="{{static}}/images/hotdogmenu.png" height="29" width="29" alt="" | 77 <img src="{{static}}/images/hotdogmenu.png" height="29" width="29" alt="" |
78 class="nomargin" /> | 78 class="nomargin" /> |
79 and select <b>Extensions</b> from the <b>Tools</b> menu. | 79 and select <b>Extensions</b> from the <b>Tools</b> menu. |
80 If there's a "+" next to "Developer mode", | 80 Ensure that the "Developer mode" checkbox in the top right-hand corner |
81 click the "+" so it turns into a "-". | 81 is checked. |
82 Now you can reload extensions, | 82 Now you can reload extensions, |
83 load an unpacked directory of files as if it were a packaged extension, | 83 load an unpacked directory of files as if it were a packaged extension, |
84 and more. For a complete tutorial, see | 84 and more. For a complete tutorial, see |
85 <a href="http://code.google.com/chrome/extensions/getstarted.html">Getting Sta rted</a>. | 85 <a href="http://code.google.com/chrome/extensions/getstarted.html">Getting Sta rted</a>. |
86 </p> | 86 </p> |
87 | 87 |
88 <h3 id="faq-gen-02">What technologies are used to write extensions for Chrome?</ h3> | 88 <h3 id="faq-gen-02">What technologies are used to write extensions for Chrome?</ h3> |
89 <p> | 89 <p> |
90 Extensions are written using the same standard web | 90 Extensions are written using the same standard web |
91 technologies that developers use to create websites. HTML is used as a | 91 technologies that developers use to create websites. HTML is used as a |
(...skipping 131 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
223 <p> | 223 <p> |
224 Yes, extensions may pass messages to other extensions. See the | 224 Yes, extensions may pass messages to other extensions. See the |
225 <a href="messaging.html#external">message passing documentation</a> | 225 <a href="messaging.html#external">message passing documentation</a> |
226 for more information. | 226 for more information. |
227 </p> | 227 </p> |
228 | 228 |
229 <h3 id="faq-dev-13">Can extensions use Google Analytics?</h3> | 229 <h3 id="faq-dev-13">Can extensions use Google Analytics?</h3> |
230 <p> | 230 <p> |
231 Yes, since extensions are built just like websites, they can use | 231 Yes, since extensions are built just like websites, they can use |
232 <a href="http://www.google.com/analytics/">Google Analytics</a> to track | 232 <a href="http://www.google.com/analytics/">Google Analytics</a> to track |
233 usage. However, we strongly advise you to modify the tracking code to pull | 233 usage. However, you have to modify the tracking code to pull |
Mike West
2013/02/11 08:21:53
Please change "have" to "must" for clarity.
方觉(Fang Jue)
2013/02/11 11:37:54
Done.
| |
234 an HTTPS version of the Google Analytics library. See | 234 an HTTPS version of the Google Analytics library. See |
235 <a href="tut_analytics.html">this tutorial</a> for more information on doing | 235 <a href="tut_analytics.html">this tutorial</a> for more information on doing |
236 this. | 236 this. |
237 </p> | 237 </p> |
238 | 238 |
239 <h3 id="faq-dev-15">Can extensions modify chrome:// URLs?</h3> | 239 <h3 id="faq-dev-15">Can extensions modify chrome:// URLs?</h3> |
240 <p> | 240 <p> |
241 No. The extensions APIs have been designed to minimize backwards | 241 No. The extensions APIs have been designed to minimize backwards |
242 compatibility issues that can arise when new versions of the browser are | 242 compatibility issues that can arise when new versions of the browser are |
243 pushed. Allowing content scripts on <code>chrome://</code> | 243 pushed. Allowing content scripts on <code>chrome://</code> |
(...skipping 224 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
468 <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions/t opics"> | 468 <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions/t opics"> |
469 discussion group</a> with a link back to your request. | 469 discussion group</a> with a link back to your request. |
470 </li> | 470 </li> |
471 <li> | 471 <li> |
472 If you originally reported your request on the discussion group and were | 472 If you originally reported your request on the discussion group and were |
473 directed to this FAQ entry, reply to your original thread with a link | 473 directed to this FAQ entry, reply to your original thread with a link |
474 to the ticket you starred or opened. This will make it easier for others | 474 to the ticket you starred or opened. This will make it easier for others |
475 with the same request to find the correct ticket. | 475 with the same request to find the correct ticket. |
476 </li> | 476 </li> |
477 </ol> | 477 </ol> |
OLD | NEW |