Right now we have a `pwmgr_form_autofill_result` histogram but since there are so many arguments to this function and ways that it can be invoked, it makes it hard to extract meaning from the data e.g. separating autofill on page load vs. autofill from autocomplete vs. autofill from the context menu. With event telemetry we can record more of this info in "extra" arguments on the event. My main concern would be that the volume of events would be too high but we can check that.
Bug 1621520 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Right now we have a `pwmgr_form_autofill_result` histogram but since there are so many arguments to this function and ways that it can be invoked, it makes it hard to extract meaning from the data e.g. separating autofill on page load vs. autofill from autocomplete vs. autofill from the context menu. Even more importantly is that currently we can only record one reason for not autofilling but ideally we would want to know all of the reason since fixing that one may not be enough to get that form to then autofill. With event telemetry we can record more of this info in "extra" arguments on the event. My main concern would be that the volume of events would be too high but we can check that.
Right now we have a `pwmgr_form_autofill_result` histogram but since there are so many arguments to this function and ways that it can be invoked, it makes it hard to extract meaning from the data ~~~e.g. separating autofill on page load vs. autofill from autocomplete vs. autofill from the context menu~~~ (this probe is only recorded for autofill without user interaction currently but that means we don't know anything about fills via the context menu or autocomplete which this bug should fix). Even more importantly is that currently we can only record one reason for not autofilling but ideally we would want to know all of the reason since fixing that one may not be enough to get that form to then autofill. With event telemetry we can record more of this info in "extra" arguments on the event. My main concern would be that the volume of events would be too high but we can check that.