Show human readable origin for Android apps

chrome/browser/resources/settings/passwords_and_forms_page/password_edit_dialog.html

Index: chrome/browser/resources/settings/passwords_and_forms_page/password_edit_dialog.html
diff --git a/chrome/browser/resources/settings/passwords_and_forms_page/password_edit_dialog.html b/chrome/browser/resources/settings/passwords_and_forms_page/password_edit_dialog.html
index 5f660a412775569d2b77466ecf12886896bb5e69..ae045c86053a5b8bbfccc11f7b45f51aa159e1e9 100644
--- a/chrome/browser/resources/settings/passwords_and_forms_page/password_edit_dialog.html
+++ b/chrome/browser/resources/settings/passwords_and_forms_page/password_edit_dialog.html
@@ -40,7 +40,7 @@
       <div class="title">$i18n{passwordDetailsTitle}</div>
       <div class="body">
         <paper-input id="websiteInput" label="$i18n{editPasswordWebsiteLabel}"
-            value="[[item.loginPair.originUrl]]" readonly always-float-label
+            value="[[item.loginPair.urls.originUrl]]" readonly always-float-label

[jdoerrie, 2017/04/21 18:48:48]

Unfortunately this will stay ugly for Android credentials, but the only
alternative I saw was to use shownUrl here, which would hide the Scheme for
regular credentials. I think showing the scheme and having ugly Android
credentials here is the better option for now. WDYT?

[hcarmona, 2017/04/21 19:07:55]

I'm about 50/50 on this. |shownUrl| sounds good b/c it's readable.
|originUrl| also sounds good because a user can copy it if they need to.

I defer to your judgement here on what is best.

[jdoerrie, 2017/04/21 20:08:25]

I went for |link| in the end, because it gives us the best of both worlds. It
hides implementation details from |origin|, but still shows full URLs. I added
now also the link to the play store for apps where we don't have information
about the affiliated website.

             on-tap="onReadonlyInputTap_">
         </paper-input>
         <paper-input id="usernameInput" label="$i18n{editPasswordUsernameLabel}"