[M57] Eliminate PasswordAutofillAgentConstructed() in mojo interface PasswordManagerDriver

[M57] Eliminate PasswordAutofillAgentConstructed() in mojo interface PasswordManagerDriver

PasswordAutofillAgentConstructed() is just for autofill::PasswordAutofillAgent to
get logging state from browser side when PasswordAutofillAgent is created.
It's useful before due to lack of pending mechanism for legacy IPCs,
but now in mojo world we can achieve this goal without it.

This CL lets browser side just send logging state as soon as it's ready,
even at that timing point renderer process has not started or has not created
PasswordAutofillAgent, the mojo call
autofill::mojom::PasswordAutofillAgent::SetLoggingState() will be cached
inside mojo message pipe and be executed immediately once PasswordAutofillAgent
instantiates and binds itself with the pending mojo connection.

This keeps exactly the same behavior with before:
autofill::mojom::PasswordAutofillAgent::SetLoggingState() is always the first
mojo call arriving at autofill::PasswordAutofillAgent from browser side.

BUG=676814
TEST=components_unittests
TBR=vabr@chromium.org,tsepez@chromium.org

Review-Url: https://codereview.chromium.org/2680163006
Cr-Commit-Position: refs/heads/master@{#450171}
(cherry picked from commit 2364c1b8adb850f0d1b1e29f16ecfd75679280d5)

Review-Url: https://codereview.chromium.org/2697803002 .
Cr-Commit-Position: refs/branch-heads/2987@{#496}
Cr-Branched-From: ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943}
Committed: https://chromium.googlesource.com/chromium/src/+/3cfb799c32b29c6c499636de1303e5fbbbdd92f5

[leonhsl(Using Gerrit), 2017-02-14 09:44:27]

Description was changed from

==========
[M57] Eliminate PasswordAutofillAgentConstructed() in mojo interface
PasswordManagerDriver

PasswordAutofillAgentConstructed() is just for autofill::PasswordAutofillAgent
to
get logging state from browser side when PasswordAutofillAgent is created.
It's useful before due to lack of pending mechanism for legacy IPCs,
but now in mojo world we can achieve this goal without it.

This CL lets browser side just send logging state as soon as it's ready,
even at that timing point renderer process has not started or has not created
PasswordAutofillAgent, the mojo call
autofill::mojom::PasswordAutofillAgent::SetLoggingState() will be cached
inside mojo message pipe and be executed immediately once PasswordAutofillAgent
instantiates and binds itself with the pending mojo connection.

This keeps exactly the same behavior with before:
autofill::mojom::PasswordAutofillAgent::SetLoggingState() is always the first
mojo call arriving at autofill::PasswordAutofillAgent from browser side.

BUG=676814
TEST=components_unittests
TBR=vabr@chromium.org,tsepez@chromium.org

Review-Url: https://codereview.chromium.org/2680163006
Cr-Commit-Position: refs/heads/master@{#450171}
(cherry picked from commit 2364c1b8adb850f0d1b1e29f16ecfd75679280d5)
==========

to

==========
[M57] Eliminate PasswordAutofillAgentConstructed() in mojo interface
PasswordManagerDriver

PasswordAutofillAgentConstructed() is just for autofill::PasswordAutofillAgent
to
get logging state from browser side when PasswordAutofillAgent is created.
It's useful before due to lack of pending mechanism for legacy IPCs,
but now in mojo world we can achieve this goal without it.

This CL lets browser side just send logging state as soon as it's ready,
even at that timing point renderer process has not started or has not created
PasswordAutofillAgent, the mojo call
autofill::mojom::PasswordAutofillAgent::SetLoggingState() will be cached
inside mojo message pipe and be executed immediately once PasswordAutofillAgent
instantiates and binds itself with the pending mojo connection.

This keeps exactly the same behavior with before:
autofill::mojom::PasswordAutofillAgent::SetLoggingState() is always the first
mojo call arriving at autofill::PasswordAutofillAgent from browser side.

BUG=676814
TEST=components_unittests
TBR=vabr@chromium.org,tsepez@chromium.org

Review-Url: https://codereview.chromium.org/2680163006
Cr-Commit-Position: refs/heads/master@{#450171}
(cherry picked from commit 2364c1b8adb850f0d1b1e29f16ecfd75679280d5)

Review-Url: https://codereview.chromium.org/2697803002 .
Cr-Commit-Position: refs/branch-heads/2987@{#496}
Cr-Branched-From:
ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943}
Committed:
https://chromium.googlesource.com/chromium/src/+/3cfb799c32b29c6c499636de1303...
==========

[leonhsl(Using Gerrit), 2017-02-14 09:44:31]

Committed patchset #1 (id:1) manually as
3cfb799c32b29c6c499636de1303e5fbbbdd92f5 (presubmit successful).

[vabr (Chromium), 2017-02-17 14:01:12]

lgtm