REPRODUCIBILITY (% or how often): 100
BUILD ID = OS VERSION (Settings > About product): 4.1.0.23
HARDWARE (XA2, Xperia 10…): X, all?
UI LANGUAGE: en
REGRESSION: (compared to previous public release: Yes, No, ?): -
DESCRIPTION:
the (new?) search engine selection in browser stores new search engines from any site even when visited in private mode
PRECONDITIONS:
using 4.1.0
STEPS TO REPRODUCE:
- open tab in private mode (e.g. github.com)
- use the search field (maybe not needed at all)
- close the browser, reopen and go to the settings - search engine selection
EXPECTED RESULT:
search engine from pivate tab is not stored
ACTUAL RESULT:
private tab info, the search engine, is stored
ADDITIONAL INFORMATION:
(Please ALWAYS attach relevant data such as logs, screenshots, etc…)
1 Like
Found as well a workaround and post it here as I do not believe storing stuff from private tabs should be stored at all.
The available (to be configured to use) search engines are stored in dconf value
/apps/sailfish-browser/settings/search_engines_available
Store/save your config in a file
dconf read /apps/sailfish-browser/settings/search_engines_available > sea
and you can load it back with
dconf write /apps/sailfish-browser/settings/search_engines_available "$(cat sea)"
or just reset it to default
dconf reset /apps/sailfish-browser/settings/search_engines_available
@tomin
Thanks for moving, must have somehow mixed up 
No change in 4.2.0…
Has this been noticed at all by @jolla?
It would be really nice if we guinea pigs could at least get any kind of info regarding our time allotted to find / report / workaround all those bugs… (I know old discussion but if nothing changes one still needs to ask 'one more time’s).
Tagging could help
Tracked by Jolla (as on TJC)
Manual note by @jovirkku
…