Expose passwords to JavaScript in Credential Manager API

third_party/WebKit/Source/core/frame/Deprecation.cpp

Index: third_party/WebKit/Source/core/frame/Deprecation.cpp
diff --git a/third_party/WebKit/Source/core/frame/Deprecation.cpp b/third_party/WebKit/Source/core/frame/Deprecation.cpp
index 725b5afe7ad21b4590ef4f8311a7655751744fff..bec519a8965d2cf897a40d4d7ac0797dc649a0a6 100644
--- a/third_party/WebKit/Source/core/frame/Deprecation.cpp
+++ b/third_party/WebKit/Source/core/frame/Deprecation.cpp
@@ -414,6 +414,26 @@ String Deprecation::DeprecationMessage(UseCounter::Feature feature) {
       return willBeRemoved("SVGPathElement.getPathSegAtLength", M62,
                            "5638783282184192");
 
+    // TODO(jdoerrie): Create separate Chrome Platform Status entry.
+    case UseCounter::kCredentialManagerIdName:
+      return willBeRemoved("PasswordCredential.idName", M62,
+                           "5026422640869376");
+
+    // TODO(jdoerrie): Create separate Chrome Platform Status entry.
+    case UseCounter::kCredentialManagerPasswordName:
+      return willBeRemoved("PasswordCredential.passwordName", M62,
+                           "5026422640869376");
+
+    // TODO(jdoerrie): Create separate Chrome Platform Status entry.
+    case UseCounter::kCredentialManagerAdditionalData:
+      return willBeRemoved("PasswordCredential.additionalData", M62,
+                           "5026422640869376");
+
+    // TODO(jdoerrie): Create separate Chrome Platform Status entry.
+    case UseCounter::kCredentialManagerCustomFetch:
+      return willBeRemoved("fetch.RequestInit.RequestCredentials.password", M62,

[Mike West, 2017/05/04 11:13:33]

We'll want a friendlier deprecation message than this produces, pointing
developers to the new `.password` attribute. It's also going to require some
rework for developers who have invested in the `fetch()` workflow, so it's
probably worth talking to folks about putting together a short migration article
to which we can point developers, showing them a drop-in replacement for the
`fetch()` flow. That is, instead of:

```
c.idName = "id";
c.passwordName = "password";
c.additionalData = formData;
fetch(url, { credentials: c, method: "POST" });
```

they'd want something like:

```
formData.set("id", c.id);
formData.set("password", c.password);
fetch(url, { credentials: "include", body: formData, method: "POST" });
```

[jdoerrie, 2017/05/04 14:24:10]

Acknowledged.

+                           "5026422640869376");
+
     // Features that aren't deprecated don't have a deprecation message.
     default:
       return String();