Expose passwords to JavaScript in Credential Manager API

third_party/WebKit/LayoutTests/external/wpt/credential-management/idl.https.html

Index: third_party/WebKit/LayoutTests/external/wpt/credential-management/idl.https.html
diff --git a/third_party/WebKit/LayoutTests/external/wpt/credential-management/idl.https.html b/third_party/WebKit/LayoutTests/external/wpt/credential-management/idl.https.html
index bc779d069e9002807c98e48d31e67ad9860cdeab..70e2d04b1cbd7f5db52eeae99e14ae17d79572f1 100644
--- a/third_party/WebKit/LayoutTests/external/wpt/credential-management/idl.https.html
+++ b/third_party/WebKit/LayoutTests/external/wpt/credential-management/idl.https.html
@@ -66,6 +66,7 @@
       attribute USVString passwordName;
 
       attribute CredentialBodyType? additionalData;

[Mike West, 2017/05/08 11:01:57]

Please drop these three attributes from this test, as it will be upstreamed and
should reflect the state of the spec and not the state of Chrome.

[jdoerrie, 2017/05/08 14:03:17]

Will do this as well. Currently I am getting a presubmit error after I removed
the attributes and the appropriate lines from the *-expected.txt file: 

** Presubmit ERRORS **
* The following files are passing testharness results without console error
messages, they should be removed:

//third_party/WebKit/LayoutTests/external/wpt/credential-management/idl.https-expected.txt
ERROR: found passing testharness results without console error messages.

From the looks of it it's complaining that there is no line with FAIL in that
file anymore.  The corresponding script
(https://codesearch.chromium.org/chromium/src/third_party/WebKit/Tools/Scripts...)
states the following:

"""Check if a LayoutTest expected file is a passing testharness result.

The intent of this script is to identify expected files that are passing
testharness.js results. Those files are not needed because the test
infrastructure will read the output of testharness.js tests if there is no
expected files."""

Is it fine to simply go ahead and remove the *-expected.txt file? I don't fully
understand this test framework yet, but removing the expectation file seems
wrong to me. What do you think?

+      readonly attribute DOMString password;
     };
     PasswordCredential implements CredentialUserData;