Simplify debugging of failure to fill |
||
Issue descriptionLet's make it a bit simpler to detect the reasons why Chrome does not fill a credential into a form by adding log-statements to chrome://password-manager-internals
,
Dec 11
,
Dec 11
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/27cb431ed301257f747c0decfe6bc55e1264321c commit 27cb431ed301257f747c0decfe6bc55e1264321c Author: Dominic Battre <battre@chromium.org> Date: Tue Dec 11 18:37:54 2018 Logging improvements for chrome://password-manager-internals This CL introduces two minor improvements to the data produced in chrome://password-manager-internals: 1. The renderer ids are printed for new password elements. 2. For forms that are given to the new form parser, the form signature is printed. This makes it a bit easier to search for data that belongs together. Bug: 913516 Change-Id: Ia1392e0b1f70bab6aa5e6348a10946d1c53046e5 Reviewed-on: https://chromium-review.googlesource.com/c/1371812 Commit-Queue: Dominic Battré <battre@chromium.org> Reviewed-by: Vadym Doroshenko <dvadym@chromium.org> Cr-Commit-Position: refs/heads/master@{#615601} [modify] https://crrev.com/27cb431ed301257f747c0decfe6bc55e1264321c/components/autofill/core/common/save_password_progress_logger.cc [modify] https://crrev.com/27cb431ed301257f747c0decfe6bc55e1264321c/components/autofill/core/common/save_password_progress_logger.h [modify] https://crrev.com/27cb431ed301257f747c0decfe6bc55e1264321c/components/password_manager/core/browser/browser_save_password_progress_logger.cc |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Dec 10