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

Side by Side Diff: chrome/common/extensions/docs/static/content_scripts.html

Issue 430003: Revert change that disallowed content scripts access to file:// (Closed)
Patch Set: Can't go back, only through Created 11 years, 1 month 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
OLDNEW
1 <div id="pageData-title" class="pageData">Content Scripts</div> 1 <div id="pageData-title" class="pageData">Content Scripts</div>
2 <div id="pageData-showTOC" class="pageData">true</div> 2 <div id="pageData-showTOC" class="pageData">true</div>
3 3
4 <p> 4 <p>
5 Content scripts are JavaScript files that run in the context of web pages. 5 Content scripts are JavaScript files that run in the context of web pages.
6 By using the standard 6 By using the standard
7 <a href="http://www.w3.org/TR/DOM-Level-2-HTML/">Document 7 <a href="http://www.w3.org/TR/DOM-Level-2-HTML/">Document
8 Object Model</a> (DOM), 8 Object Model</a> (DOM),
9 they can read details of the web pages the browser visits, 9 they can read details of the web pages the browser visits,
10 or make changes to them. 10 or make changes to them.
(...skipping 22 matching lines...) Expand all
33 </li> 33 </li>
34 <li> 34 <li>
35 Use variables or functions defined by their extension's pages 35 Use variables or functions defined by their extension's pages
36 </li> 36 </li>
37 <li> 37 <li>
38 Use variables or functions defined by web pages or by other content scripts 38 Use variables or functions defined by web pages or by other content scripts
39 </li> 39 </li>
40 <li> 40 <li>
41 Make cross-site XMLHttpRequests 41 Make cross-site XMLHttpRequests
42 </li> 42 </li>
43 <li>
44 Execute on file:// urls.
45 </li>
46 </ul> 43 </ul>
47 44
48 <p> 45 <p>
49 These limitations aren't as bad as they sound. 46 These limitations aren't as bad as they sound.
50 Content scripts can <em>indirectly</em> use the chrome.* APIs, 47 Content scripts can <em>indirectly</em> use the chrome.* APIs,
51 get access to extension data, 48 get access to extension data,
52 and request extension actions 49 and request extension actions
53 by exchanging <a href="messaging.html">messages</a> 50 by exchanging <a href="messaging.html">messages</a>
54 with their parent extension. 51 with their parent extension.
55 Content scripts can also 52 Content scripts can also
(...skipping 148 matching lines...) Expand 10 before | Expand all | Expand 10 after
204 just like you would any other URL, 201 just like you would any other URL,
205 as the following code shows. 202 as the following code shows.
206 </p> 203 </p>
207 204
208 205
209 <pre> 206 <pre>
210 <em>//Code for displaying &lt;extensionDir>/images/myimage.png:</em> 207 <em>//Code for displaying &lt;extensionDir>/images/myimage.png:</em>
211 var imgURL = <b>chrome.extension.getURL("images/myimage.png")</b>; 208 var imgURL = <b>chrome.extension.getURL("images/myimage.png")</b>;
212 document.getElementById("someImage").src = imgURL; 209 document.getElementById("someImage").src = imgURL;
213 </pre> 210 </pre>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698