chrome/common/extensions/docs/tut_oauth.html - Issue 2881038: Extension doc changes (nothing buildable or testable) - Add boilerplate line for experimental api...

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

Issue 2881038: Extension doc changes (nothing buildable or testable) - Add boilerplate line for experimental api... (Closed) Base URL: http://src.chromium.org/git/chromium.git

Patch Set: render docs Created 10 years, 4 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

OLD	NEW
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 273 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
284 <a href="#id-anchor">id</a>	284 <a href="#id-anchor">id</a>

285 </li>	285 </li>

286 </ol>	286 </ol>

287 </li>	287 </li>

288 </ol>	288 </ol>

289 </li>	289 </li>

290 </ol>	290 </ol>

291 </div>	291 </div>

292 <!-- /TABLE OF CONTENTS -->	292 <!-- /TABLE OF CONTENTS -->

293	293

	294 <!-- Standard content lead-in for experimental API pages -->

	295 <p id="classSummary" style="display: none; ">

	296 For information on how to use experimental APIs, see the <a href="expe rimental.html">chrome.experimental.* APIs</a> page.

	297 </p>

	298

294 <!-- STATIC CONTENT PLACEHOLDER -->	299 <!-- STATIC CONTENT PLACEHOLDER -->

295 <div id="static"><div id="pageData-name" class="pageData">Tutorial: OAut h</div>	300 <div id="static"><div id="pageData-name" class="pageData">Tutorial: OAut h</div>

296 <div id="pageData-showTOC" class="pageData">true</div>	301 <div id="pageData-showTOC" class="pageData">true</div>

297	302

298 <p>	303 <p>

299 <a href="http://oauth.net/">OAuth</a> is an open protocol that aims to standardi ze the way desktop and web applications access a user's private data. OAuth prov ides a mechanism for users to grant access to private data without sharing their private credentials (username/password). Many sites have started enabling APIs to use OAuth because of its security and standard set of libraries.	304 <a href="http://oauth.net/">OAuth</a> is an open protocol that aims to standardi ze the way desktop and web applications access a user's private data. OAuth prov ides a mechanism for users to grant access to private data without sharing their private credentials (username/password). Many sites have started enabling APIs to use OAuth because of its security and standard set of libraries.

300 </p>	305 </p>

301 <p>	306 <p>

302 This tutorial will walk you through the necessary steps for creating a Google Ch rome Extension that uses OAuth to access an API. It leverages a library that you can reuse in your extensions.	307 This tutorial will walk you through the necessary steps for creating a Google Ch rome Extension that uses OAuth to access an API. It leverages a library that you can reuse in your extensions.

303 </p>	308 </p>

(...skipping 367 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
671 _uff=0;	676 _uff=0;

672 urchinTracker();	677 urchinTracker();

673 }	678 }

674 catch(e) {/* urchinTracker not available. */}	679 catch(e) {/* urchinTracker not available. */}

675 </script>	680 </script>

676 <!-- end analytics -->	681 <!-- end analytics -->

677 </div>	682 </div>

678 </div> <!-- /gc-footer -->	683 </div> <!-- /gc-footer -->

679 </div> <!-- /gc-container -->	684 </div> <!-- /gc-container -->

680 </body></html>	685 </body></html>

OLD	NEW

« no previous file with comments | « chrome/common/extensions/docs/tut_debugging.html ('k') | chrome/common/extensions/docs/tutorials.html » ('j') | no next file with comments »