Chrome Version: 58.*
OS: Linux

What steps will reproduce the problem?
(1) Do not sign-in to Chrome.
(2) Visit dump-truck.appspot.com and fill forms with default values and submit.
(3) Chrome should offer to save card locally (See: https://cs.chromium.org/chromium/src/components/autofill/core/browser/autofill_manager.cc?l=1232&rcl=4dd065a3be8399b968ae44e93f1997254c173e84)

(4) Save a card on payments.google.com
(5) Sign-to Chrome
(6) Visit dump-truck.appspot.com and fill form by unmasking a card saved in step (4).
(7) Chrome will not offer to save the card locally (See: https://cs.chromium.org/chromium/src/components/autofill/core/browser/autofill_experiments.cc?l=162&rcl=4dd065a3be8399b968ae44e93f1997254c173e84)

What is the expected result?

We should either allow both saves or neither. What is the difference (security-wise) between these 2 cases?

What happens instead?

We only offer save for local cards, not unmasked server cards.