However, a bug needs to be filed to have the Enable Keywords item actually work, another bug from paulmac... am presuming that keyword.enable should go into the prefs.js file --but correct me if am wrong. "The pref is called keyword.enabled and will be set to true by default. The comma-separated list pref will probably not be in for beta, a bug should be filed to track this. This will be an ugly one, because I don't think keywords will be enabled for the mozilla product, just commercial."
This is a bug to hook it up in the Pref UI. Bug 23211 deals with turning it on by default, which jud has.
We probably need this for beta1 ...
Putting on PDT+ radar for beta1.
I have a fix for this that jud reviewed. Index: pref-smart_browsing.xul =================================================================== RCS file: /cvsroot/mozilla/xpfe/components/prefwindow/resources/content/pref-smart_browsin g.xul,v retrieving revision 1.18 diff -r1.18 pref-smart_browsing.xul 88c88 < pref="true" preftype="bool" prefstring="browser.goBrowsing.enabled"/> --- > pref="true" preftype="bool" prefstring="keyword.enabled"/>
so just to be clear, the pref should show up in both mozilla and netscape builds, but should be off (unchecked) in mozilla and on (checked) in netscape?
You are correct my friend.
looks fine. verif w/linux comm bits, 2000-02-09-08.
oops: forgot to check: yes, on the comm builds for mac and win, the Enabled Keywords is selected. and all platforms using the non-comm mozilla bits (and a new/default profile), that checkbox is *not* selected.
Bulk moving Pref UI bugs to new component Preferences.