Linking AvailabilityFinder with APIDataSource and intro-table templates.

chrome/common/extensions/docs/templates/json/api_availabilities.json

Index: chrome/common/extensions/docs/templates/json/api_availabilities.json
diff --git a/chrome/common/extensions/docs/templates/json/api_availabilities.json b/chrome/common/extensions/docs/templates/json/api_availabilities.json
index a81f194de4b5ad4aca434421f55cfd9b21651a09..53d407ca30bfa58eb6fc7c2f3913ab614c943c83 100644
--- a/chrome/common/extensions/docs/templates/json/api_availabilities.json
+++ b/chrome/common/extensions/docs/templates/json/api_availabilities.json
@@ -1,3 +1,7 @@
+// Availability for these APIs either can't be accurately found or would take a
+// significant amount of specific logic to determine (devtools).
+// The versions listed here were drawn either from hardcoded HTML intro tables
+// or from the whats_new page.

[epeterson, 2013/07/16 00:28:23]

added some comments to api_availabilities, so they're not AS arbitrary.

 {
   "devtools.inspectedWindow": {
     "channel": "stable",
@@ -11,7 +15,23 @@
     "channel": "stable",
     "version": 18
   },
+  "input.ime": {
+    // Generated availability of version 18.

[not at google - send to devlin, 2013/07/16 22:25:00]

myeh, these "Generated..." comments are confusing.

[epeterson, 2013/07/17 23:48:23]

You're right, they don't really help anyone much.
And trying to explain the details of the availability algorithm within this file
would likely be confusing as well.

+    "channel": "stable",
+    "version": 21
+  },
+  "storage": {
+    // Generated availability of version 19.
+    "channel": "stable",
+    "version": 20
+  },
+  "pageCapture": {
+    // Generated availability of version 17.
+    "channel": "stable",
+    "version": 18
+  },
   "webstore": {
+    // Only 'webstorePrivate' is present before version 19.
     "channel": "stable",
     "version": 15
   }