Index: chrome/common/extensions/docs/templates/articles/manifest/file_handlers.html |
diff --git a/chrome/common/extensions/docs/templates/articles/manifest/file_handlers.html b/chrome/common/extensions/docs/templates/articles/manifest/file_handlers.html |
index b7cd44c77d5c8e5875c506560d44cdadd988a1fa..1e11fba43bf750024723318ee84575a2a348b4a4 100644 |
--- a/chrome/common/extensions/docs/templates/articles/manifest/file_handlers.html |
+++ b/chrome/common/extensions/docs/templates/articles/manifest/file_handlers.html |
@@ -1,7 +1,7 @@ |
<h1 id="file_handlers">Manifest - File Handlers</h1> |
<p> |
-Used by <a href="../app_lifecycle.html#eventpage">packaged apps</a> |
+Used by <a href="../app_lifecycle#eventpage">packaged apps</a> |
to specify what types of files the app can handle. An app can have multiple <code>file_handlers</code>, with each one having an identifier, a list of MIME types and/or a list of file extensions that can be handled, and |
a title. Here's an example of specifying file handlers: |
</p> |
@@ -38,5 +38,5 @@ To handle files, apps also need to declare the $(ref:fileSystem) |
permission. Apps can then be passed files in the $(ref:app.runtime.onLaunched) |
event - either from the system |
file manager (currently supported on ChromeOS only) or by providing |
-a path on the <a href="../first_app.html#open">command line</a>. |
+a path on the <a href="../first_app#open">command line</a>. |
</p> |