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

Side by Side Diff: chrome/common/extensions/docs/match_patterns.html

Issue 8800006: Support chrome-extension:// scheme in URLPattern. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Created 9 years 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 <!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note: 1 <!DOCTYPE html><!-- This page is a placeholder for generated extensions api doc. Note:
2 1) The <head> information in this page is significant, should be uniform 2 1) The <head> information in this page is significant, should be uniform
3 across api docs and should be edited only with knowledge of the 3 across api docs and should be edited only with knowledge of the
4 templating mechanism. 4 templating mechanism.
5 3) All <body>.innerHTML is genereated as an rendering step. If viewed in a 5 3) All <body>.innerHTML is genereated as an rendering step. If viewed in a
6 browser, it will be re-generated from the template, json schema and 6 browser, it will be re-generated from the template, json schema and
7 authored overview content. 7 authored overview content.
8 4) The <body>.innerHTML is also generated by an offline step so that this 8 4) The <body>.innerHTML is also generated by an offline step so that this
9 page may easily be indexed by search engines. 9 page may easily be indexed by search engines.
10 --><html xmlns="http://www.w3.org/1999/xhtml"><head> 10 --><html xmlns="http://www.w3.org/1999/xhtml"><head>
(...skipping 326 matching lines...) Expand 10 before | Expand all | Expand 10 after
337 a content script's section of the manifest, 337 a content script's section of the manifest,
338 as well as in the <code>"exclude_matches"</code> section. 338 as well as in the <code>"exclude_matches"</code> section.
339 This page describes the match pattern syntax — 339 This page describes the match pattern syntax —
340 the rules you need to follow when you specify 340 the rules you need to follow when you specify
341 which URLs your content script affects. 341 which URLs your content script affects.
342 </p> 342 </p>
343 343
344 <p> 344 <p>
345 A match pattern is essentially a URL 345 A match pattern is essentially a URL
346 that begins with a permitted scheme (<code>http</code>, 346 that begins with a permitted scheme (<code>http</code>,
347 <code>https</code>, <code>file</code>, or <code>ftp</code>), 347 <code>https</code>, <code>file</code>, <code>ftp</code>, or
348 <code>chrome-extension</code>),
battre 2011/12/05 14:23:08 There are other schemes that were permitted but no
348 and that can contain '<code>*</code>' characters. 349 and that can contain '<code>*</code>' characters.
349 The special pattern 350 The special pattern
350 <code>&lt;all_urls&gt;</code> matches any URL 351 <code>&lt;all_urls&gt;</code> matches any URL
351 that starts with a permitted scheme. 352 that starts with a permitted scheme.
352 Each match pattern has 3 parts:</p> 353 Each match pattern has 3 parts:</p>
353 <p></p> 354 <p></p>
354 355
355 <ul> 356 <ul>
356 <li> <em>scheme</em> — 357 <li> <em>scheme</em> —
357 for example, <code>http</code> or <code>file</code> 358 for example, <code>http</code> or <code>file</code>
(...skipping 14 matching lines...) Expand all
372 </li> 373 </li>
373 <li> <em>path</em> — 374 <li> <em>path</em> —
374 for example, <code>/*</code>, <code>/foo* </code>, 375 for example, <code>/*</code>, <code>/foo* </code>,
375 or <code>/foo/bar </code> 376 or <code>/foo/bar </code>
376 </li> 377 </li>
377 </ul> 378 </ul>
378 379
379 <p>Here's the basic syntax:</p> 380 <p>Here's the basic syntax:</p>
380 381
381 <pre><em>&lt;url-pattern&gt;</em> := <em>&lt;scheme&gt;</em>://<em>&lt;host&gt;< /em><em>&lt;path&gt;</em> 382 <pre><em>&lt;url-pattern&gt;</em> := <em>&lt;scheme&gt;</em>://<em>&lt;host&gt;< /em><em>&lt;path&gt;</em>
382 <em>&lt;scheme&gt;</em> := '*' | 'http' | 'https' | 'file' | 'ftp' 383 <em>&lt;scheme&gt;</em> := '*' | 'http' | 'https' | 'file' | 'ftp' | 'chrome-ext ension'
383 <em>&lt;host&gt;</em> := '*' | '*.' <em>&lt;any char except '/' and '*'&gt;</em> + 384 <em>&lt;host&gt;</em> := '*' | '*.' <em>&lt;any char except '/' and '*'&gt;</em> +
384 <em>&lt;path&gt;</em> := '/' <em>&lt;any chars&gt;</em> 385 <em>&lt;path&gt;</em> := '/' <em>&lt;any chars&gt;</em>
385 </pre> 386 </pre>
386 387
387 <p> 388 <p>
388 The meaning of '<code>*</code>' depends on whether 389 The meaning of '<code>*</code>' depends on whether
389 it's in the <em>scheme</em>, <em>host</em>, or <em>path</em> part. 390 it's in the <em>scheme</em>, <em>host</em>, or <em>path</em> part.
390 If the <em>scheme</em> is <code>*</code>, 391 If the <em>scheme</em> is <code>*</code>,
391 then it matches either <code>http</code> or <code>https</code>. 392 then it matches either <code>http</code> or <code>https</code>.
392 If the <em>host</em> is just <code>*</code>, 393 If the <em>host</em> is just <code>*</code>,
(...skipping 382 matching lines...) Expand 10 before | Expand all | Expand 10 after
775 _uff=0; 776 _uff=0;
776 urchinTracker(); 777 urchinTracker();
777 } 778 }
778 catch(e) {/* urchinTracker not available. */} 779 catch(e) {/* urchinTracker not available. */}
779 </script> 780 </script>
780 <!-- end analytics --> 781 <!-- end analytics -->
781 </div> 782 </div>
782 </div> <!-- /gc-footer --> 783 </div> <!-- /gc-footer -->
783 </div> <!-- /gc-container --> 784 </div> <!-- /gc-container -->
784 </body></html> 785 </body></html>
OLDNEW
« no previous file with comments | « no previous file | chrome/common/extensions/docs/static/match_patterns.html » ('j') | content/public/common/url_constants.h » ('J')

Powered by Google App Engine
This is Rietveld 408576698