jdoerrie@: will you have a chance to fix ugly Android credentials in new settings? You know MD settings well. This fix will probably be very easy for you. I am glad to explain backend code or current settings code, if you need.
dbeam@:
I started working on this bug in http://crrev.com/2651663003, but ran into the Android issue screenshotted above. In the following discussion hcarmona@ suggested getting inspired by Autofill, similarly to this: http://screen/dQpS9auNZvR
I reached out to an UX designer who suggested the proposal shown in #c7, but I haven't followed up on it yet.
Furthermore, it would be nice to be able to display the PlayStore name of the Android app credentials are associated with. Currently we only support credentials that have |affiliated_web_realm| set (https://cs.chromium.org/chromium/src/components/autofill/core/common/password_form.h?l=121). To my understanding that currently only applies to apps that opted into Smartlock (https://developers.google.com/identity/smartlock-passwords/android/associate-apps-and-sites), for example Netflix.
Mapping app identifiers to PlayStore names requires architectural changes, which is why this wasn't done yet.
However, I agree that for the mean time we should probably at least have feature parity between the old settings and MD settings and therefore not wait for PlayStore names. This however raises the question how to communicate that Android credentials have an associated web realm with JavaScript.
In the old settings we simply add the appropriate fields to the DictionaryValue that is shared with JS (https://cs.chromium.org/chromium/src/chrome/browser/ui/webui/options/password_manager_handler.cc?l=257), but this is incompatible with the IDL used for MD settings (https://cs.chromium.org/chromium/src/chrome/common/extensions/api/passwords_private.idl) and would probably require changes there.
In http://crrev.com/2651663003 I so far simply modified |entry.login_pair.origin_url|, but I don't think we should go as far and add HTML markup such as '<bdo>' there. It would be much cleaner to do this in HTML and JS only, with the appropriate metadata passed through the IDL.
What do you think is the cleanest way here, dbeam@?
Your change meets the bar and is auto-approved for M59. Please go ahead and merge the CL to branch 3071 manually. Please contact milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), gkihumba@(ChromeOS), Abdul Syed@(Desktop)
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Comment 1 by kolos@chromium.org
, Jan 19 2017