Assert @autofill::PersonalDataManager::IsExperimentalWalletIntegrationEnabled()

Any preference before being queried out needs to be set first.
In the specific case of kAutofillWalletSyncExperimentEnabled
it happens when AutofillManager::RegisterProfilePrefs is called.

However, chromium-efl is being initializing preferences on demand,
at the time "browser context" is created.
Patch adds this specific missing one.

Original beta/m42 patch:
- 165.213.202.130/gerrit/#/c/92065/ , reviewed by
Janusz Majnert, arno renevier.

Bug: http://107.108.218.239/bugzilla/show_bug.cgi?id=13114

Reviewed by: a.renevier, sns.park

Change-Id: I7af2e61bbc28fff9794206f6178d6791decbbe15
Signed-off-by: Antonio Gomes <a1.gomes@samsung.com>

diff --git a/tizen_src/ewk/efl_integration/browser_context_efl.cc b/tizen_src/ewk/efl_integration/browser_context_efl.cc
index 893cdab..2eb3502 100644 (file)
--- a/tizen_src/ewk/efl_integration/browser_context_efl.cc
+++ b/tizen_src/ewk/efl_integration/browser_context_efl.cc
@@ -134,6 +134,7 @@ BrowserContextEfl::BrowserContextEfl(EWebContext* web_context, bool incognito)
   PrefRegistrySimple* pref_registry = new PrefRegistrySimple();
 
   pref_registry->RegisterBooleanPref(kAutofillEnabled, true);
+  pref_registry->RegisterBooleanPref(kAutofillWalletSyncExperimentEnabled, false);
   pref_registry->RegisterDoublePref(kAutofillPositiveUploadRate, 0.0);
   pref_registry->RegisterDoublePref(kAutofillNegativeUploadRate, 0.0);