Closed
Bug 382968
Opened 18 years ago
Closed 12 years ago
"browser.search.defaultengine" preference embeds absolute path of application directory
Categories
(SeaMonkey :: Preferences, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: MatsPalmgren_bugz, Unassigned)
Details
"browser.search.defaultengine" preference embeds absolute path of application directory
STEPS TO REPRODUCE
1. Start Seamonkey with a fresh profile
2. type something in the URL bar, then click Search
3. File->Quit
ACTUAL RESULTS
In the prefs.js file we got:
user_pref("browser.search.defaultengine", "engine:///usr/local/seamonkey/searchplugins/google.src");
EXPECTED RESULT
In this case there should not exist a setting for "browser.search.defaultengine" since it's the default value.
In the general case, when the selected search engine isn't the initial
default value, the value should NOT embed the path to the application
that created the pref happens to be installed because it's not future
proof against format changes in the search plugin file.
Also, the pref will be reset to it's default value if the original
application directory is removed/renamed.
PLATFORMS AND BUILDS TESTED
Bug occurs in SeaMonkey trunk on Linux
Flags: blocking-seamonkey2.0a1?
Comment 1•17 years ago
|
||
(Filter "spam" on 'prefs-nobody-20080612'.)
Assignee: prefs → nobody
QA Contact: prefs
This is not blocking for a1 (and probably not for final either), any changes to how the search engine work would typically have a way of migrating existing preferences.
Flags: blocking-seamonkey2.0a1? → blocking-seamonkey2.0a1-
Comment 3•12 years ago
|
||
We moved from Sherlock search engines to OpenSearch so this pref doesn't exist any more. Closing as WONTFIX/INVALID
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•