Any search engine you want, as long as it's Google :(
Nelson Bolyard
I've discovered two things:
1) the old "smart browsing" feature, which would try appending .com to
simple words in the address bar, is now gone. Instead, the single word
is sent to google. Used to be that typing my name into the browser took
me to bolyard.com. Now it takes me to google.com, every time.
2) Doesn't matter what search engine I've chosen in the prefs, all searches
go to Google.
I protest. If Firefox wants to sell its soul to Google, so be it, but
not SeaMonkey. Not unless SM is getting LOTS of money for this, like
millions with which to hire full time developers.
I'm now completely blocking access from my home network to google because of
this. Hello, Yahoo!
Barry Edwin Gilmour
Edit/Preferences/Browser/Location_Bar/Unknown_Locations/ Add "www" and
">com" to the location if a web page is not found
be what you are looking-for? This works on SM2.0a1pre/2008062101.
All the best, Barry.
Barry Edwin Gilmour
The new Edit/Preferences/Browser/Location_Bar/Internet_Search_Engine
simply has a ticked-check-box for the sole-entry ~ Show default
search-engine,
but, the old
Edit/(Legacy_Prefwindow...)/(Migrated:_Browser)/Internet_Search/Default_Search_Engine/Search
using:
preference, gives a button with the name of the default-engine on it,
and with the drop-down-menu selector, (choice of the seven
search-engines I installed for-convenience into my personal-profile, as
each nightly clears out the system /usr/local/sm, except-for the plugins).
This drop-down menu matches the one in my sidebar search-engine selector.
Nelson, I just tested all of the search-engines with your name in the
address-bar, and results are as-follows:
OK, this will be quicker to-do by-snapshot. View the images at:--
http://www.flickr.com/photos/22198779@N03/with/2600355006/
If you click-on the image and then the "all-sizes" button, you can read
the address-bar with the pertinent info therein. Don't laugh, but I
don't use Yahoo-search. Three of the engines "Ask.com" "dmoz.org" and
"Google", do get the "www" and ".com" added-to the text-entry "bolyard".
The other four search with their own search-engines for the single
word "bolyard", no "www" or ".com" in the address-bar. Barry.
Neil
>1) the old "smart browsing" feature, which would try appending .com to simple words in the address bar, is now gone. Instead, the single word is sent to google. Used to be that typing my name into the browser took me to bolyard.com. Now it takes me to google.com, every time.
>
To support Vista's "search with default browser" feature, we turned on
the last preference in the Location Bar page by default; you may want to
turn it off again.
--
Warning: May contain traces of nuts.
Robert Kaiser
> I've discovered two things:
>
> 1) the old "smart browsing" feature, which would try appending .com to
> simple words in the address bar, is now gone. Instead, the single word
> is sent to google. Used to be that typing my name into the browser took
> me to bolyard.com. Now it takes me to google.com, every time.
>
> 2) Doesn't matter what search engine I've chosen in the prefs, all searches
> go to Google.
You can go into about:config and switch keyword.URL to some other
engine, and/or you can go the the Location Bar preferences and change
how "Unknown Locations" are handled.
Robert Kaiser
Philip Chee
Will the Internet Search prefs panel which disappeared in the migration
make a reappearance in the new prefwindow eventually?
Phil
--
Philip Chee <phi...@aleytys.pc.my>, <phili...@gmail.com>
http://flashblock.mozdev.org/ http://xsidebar.mozdev.org
Guard us from the she-wolf and the wolf, and guard us from the thief,
oh Night, and so be good for us to pass.
[ ]Peter Norton is the "Betty Crocker" of software!
* TagZilla 0.066.6
Nelson Bolyard
That's checked. Just doesn't work.
> This works on SM2.0a1pre/2008062101.
> All the best, Barry.
Thanks anyway.
Robert Kaiser
> Will the Internet Search prefs panel which disappeared in the migration
> make a reappearance in the new prefwindow eventually?
It's not disappeared, it's just not yet migrated (look into the legacy
prefwindow, everything not marked migrated there still has to be done).
Robert Kaiser
Nelson Bolyard
> Nelson, Here is a little more info:
> The new Edit/Preferences/Browser/Location_Bar/Internet_Search_Engine
> simply has a ticked-check-box for the sole-entry ~ Show default
> search-engine,
Interesting. Thanks for that pointer. I had never even noticed that.
I always use the legacy pref windows first, and only try the new pref
windows if I can't find what I want in the legacy window.
> but, the old
> Edit/(Legacy_Prefwindow...)/(Migrated:_Browser)/Internet_Search/Default_Search_Engine/Search
> using:
> preference, gives a button with the name of the default-engine on it,
> and with the drop-down-menu selector, (choice of the seven
> search-engines I installed for-convenience into my personal-profile, as
> each nightly clears out the system /usr/local/sm, except-for the plugins).
Seven, eh? I gotta figure out how to add more. I have only 3, and it
doesn't matter which one I choose. Regardless of the choice, they all
go to google. That's got me steamed.
> This drop-down menu matches the one in my sidebar search-engine selector.
> Nelson, I just tested all of the search-engines with your name in the
> address-bar, and results are as-follows:
> OK, this will be quicker to-do by-snapshot. View the images at:--
> http://www.flickr.com/photos/22198779@N03/with/2600355006/
> If you click-on the image and then the "all-sizes" button, you can read
> the address-bar with the pertinent info therein. Don't laugh, but I
> don't use Yahoo-search.
Neither do I, normally, but right now, I'm absolutely determined to put a
stop to SM's decision to send everything to google, so I've blocked access
to google from my local network entirely. When SM gives me back control
over my searches, then I'll allow the use of Google again. Not until then.
> Three of the engines "Ask.com" "dmoz.org" and
> "Google", do get the "www" and ".com" added-to the text-entry "bolyard".
> The other four search with their own search-engines for the single
> word "bolyard", no "www" or ".com" in the address-bar. Barry.
I think you're saying that the behavior I observe, going straight to the
search engine without trying .com first, is a function on which search
engine is chosen. That's certainly NOT how it worked a month ago, and
is not how I want it to work. I want it to try to add www. and .com
(and whatever other combinations it tries) before going to the search
engine, REGARDLESS of the search engine chosen.
Nelson Bolyard
Ah HA! Thanks for that explanation. Maybe that will solve my problem.
Here are some suggestions to keep long time SM users (like me) happy:
1) Don't turn that on by default except on Vista. And
2) Don't turn it on by default for old SM profiles that predate this
feature.
Nelson Bolyard
> Nelson Bolyard wrote:
>> I've discovered two things:
>>
>> 1) the old "smart browsing" feature, which would try appending .com to
>> simple words in the address bar, is now gone. Instead, the single word
>> is sent to google. Used to be that typing my name into the browser took
>> me to bolyard.com. Now it takes me to google.com, every time.
>>
>> 2) Doesn't matter what search engine I've chosen in the prefs, all searches
>> go to Google.
>
> You can go into about:config and switch keyword.URL to some other
> engine,
I have keyword.enabled set to false, but SM seems to be ignoring that!!
I'd call that a P1 regression.
> and/or you can go the the Location Bar preferences and change
> how "Unknown Locations" are handled.
I don't have any pref UI that uses the string "Unknown Locations", but
I do have "Perform a web search when entered text is not a web location".
I've just unchecked that. We'll see what effect that has.
> Robert Kaiser
Nelson Bolyard
> Barry Edwin Gilmour wrote, On 2008-06-22 04:03:
>> but, the old
>> Edit/(Legacy_Prefwindow...)/(Migrated:_Browser)/Internet_Search/Default_Search_Engine/Search
>> using:
>> preference, gives a button with the name of the default-engine on it,
>> and with the drop-down-menu selector, (choice of the seven
>> search-engines I installed for-convenience into my personal-profile, as
>> each nightly clears out the system /usr/local/sm, except-for the plugins).
>
> Seven, eh? I gotta figure out how to add more. I have only 3, and it
> doesn't matter which one I choose. Regardless of the choice, they all
> go to google. That's got me steamed.
>> Don't laugh, but I don't use Yahoo-search.
>
> Neither do I, normally, but right now, I'm absolutely determined to put a
> stop to SM's decision to send everything to google, so I've blocked access
> to google from my local network entirely. When SM gives me back control
> over my searches, then I'll allow the use of Google again. Not until then.
>
>> Three of the engines "Ask.com" "dmoz.org" and "Google",
Those are the 3 engine choices I see, and it doesn't matter which I select.
All searches go to google (or rather, it tries, but I've cut off all access
to google at the router.)
Thanks to Neil's suggestion, I unchecked the new pref
"Perform a web search when entered text is not a web location",
and that restored the behavior of trying www. and .com. (Thanks, Neil!)
So, now the remaining problem is putting a stop to all searches going
to google, even when I've selected Ask or dmoz.
Justin Wood (Callek)
Some windows XP applications utilize this feature, like "Process Explorer".
> 2) Don't turn it on by default for old SM profiles that predate this
> feature.
Unless you have changed that pref yourself, (thus making it a user pref)
there is no easy way around that.
--
~Justin Wood (Callek)
Nelson Bolyard
> but, the old
> Edit/(Legacy_Prefwindow...)/(Migrated:_Browser)/Internet_Search/Default_Search_Engine/Search using:
> preference, gives a button with the name of the default-engine on it,
> and with the drop-down-menu selector, (choice of the seven
> search-engines I installed for-convenience into my personal-profile,
How can I add my own search engine choices to that list?
I don't use sidebar, and I don't use search bar (whatever that is).
I just want to be able to do searches from the URL bar using other
search engines besides google. Yahoo would be a good start.
I've searched the web for this info. Most pages simple tell users
how they can switch between Google and Ask. Ask.com seems to now be just
another front end for Google. Most search results from ask.com are
actually links to google pages, which I have disabled at the router,
so Ask is of no interest to me.
I did find one page that initially looked promising:
http://mycroft.mozdev.org/yahoo-search-plugins.html
but these all appear to be highly specialized searches, not general
purpose web searches. :(
Do "OpenSearch" plugins work with SM 2.0a1pre?
Nelson Bolyard
> Barry Edwin Gilmour wrote, On 2008-06-22 04:03:
>
>> but, the old
>> Edit/(Legacy_Prefwindow...)/(Migrated:_Browser)/Internet_Search/Default_Search_Engine/Search using:
>> preference, gives a button with the name of the default-engine on it,
>> and with the drop-down-menu selector, (choice of the seven
>> search-engines I installed for-convenience into my personal-profile,
>
> How can I add my own search engine choices to that list?
I figured out how to create my own Sherlock search plugins. Thanks.
> Do "OpenSearch" plugins work with SM 2.0a1pre?
No, they don't. Or more exactly, the web page refuses to install them
because it believes they don't.
Tony Mechelynck
[...]
> Seven, eh? I gotta figure out how to add more. I have only 3, and it
> doesn't matter which one I choose. Regardless of the choice, they all
> go to google. That's got me steamed.
Some sites have links (javascript links, I think) that you can click to
add an engine related to that site. OTOH, http://mycroft.mozdev.org/ has
a whole collection of search engines that you can install (one by one,
after searching for what you'd like to have), including one for its own
site.
Best regards,
Tony.
--
Women who want to be equal to men lack imagination
-- Graffito in a women's restroom
Robert Kaiser
> Robert Kaiser wrote, On 2008-06-22 07:15:
>> You can go into about:config and switch keyword.URL to some other
>> engine,
>
> I have keyword.enabled set to false, but SM seems to be ignoring that!!
> I'd call that a P1 regression.
No, it doesn't. You're probably talking about two different functions:
Searching explicitely from the urlbar with the "Search" button or the
differently colored special item in the autocomplete result dropdown
(which uses the selected sherlock plugin) and the "keyword" function
that sends any string it doesn't understand to its keyword.URL when you
press Enter in the urlbar.
>> and/or you can go the the Location Bar preferences and change
>> how "Unknown Locations" are handled.
>
> I don't have any pref UI that uses the string "Unknown Locations", but
The groupbox has that label.
> I do have "Perform a web search when entered text is not a web location".
> I've just unchecked that. We'll see what effect that has.
That's keyword.enabled ;-)
Robert Kaiser
Jens Hatlak
>> Do "OpenSearch" plugins work with SM 2.0a1pre?
>
> No, they don't. Or more exactly, the web page refuses to install them
> because it believes they don't.
What will eventually become SM 2 does not (yet) support OpenSearch, see
bug 410613. Interesting here is that comment 3 suggests that Sherlock
search plugins might be removed from Mycroft in the (near?) future.
BTW: OpenSearch add-ons are wrongly displayed for SM on AMO. That's bug
439337.
HTH
Jens
--
Jens Hatlak <http://jens.hatlak.de/>
SeaMonkey Trunk Tracker <http://smtt.blogspot.com/>
Manuel Reimer
> You can go into about:config and switch keyword.URL to some other
> engine, and/or you can go the the Location Bar preferences and change
> how "Unknown Locations" are handled.
IMO this should be switched back to the old behaviour, as we already
have the "search google for" entry in our dropdown. If someone really
wants to trigger a search engine with his entry, then he just has to
press "cursor up" and "enter". We don't a second solution for web
searches from address bar.
CU
Manuel
Manuel Reimer
> Some windows XP applications utilize this feature, like "Process
> Explorer".
There should be a command line switch to trigger a search. If someone
sends an string to a browser, then this browser should handle this as
URL and should do nothing else.
This "feature" makes the nice "Search ... for" entry in the autocomplete
list obsolete. I don't think this should be enabled by default, just
because some apps do silly things such as sending plain search requests
to browsers without telling them to search for them.
CU
Manuel
Manuel Reimer
> To support Vista's "search with default browser" feature, we turned on
> the last preference in the Location Bar page by default; you may want to
> turn it off again.
It should be possible to do this just for "URLs" passed via command
line. So invalid URLs passed via command line should be always handled
as search request, but the URL bar should get the same behavior as in SM
1.x with an optional "keyword" feature. This way silly applications,
which just send plain search requests, will always work, independently
of the preference "keyword.enabled".
CU
Manuel
Manuel Reimer
> It should be possible to do this just for "URLs" passed via command
> line.
Sorry for quoting myself ;-)
It most probably *is* possible. If the default setting can be reverted
to the old default, if command line searches *always* trigger the
search, then I'll have a look at this, file a bug and (maybe) attach a
patch. In my opinion searches from command line shouldn't depend on
"keyword.enabled". Even if the user disables this, external applications
should be able to trigger a search.
CU
Manuel
--
www.jetzt-abwaehlen.de Wählen gehen 2009! Ein Aufruf etwas zu ändern.
Die letzte Stimme, die man hört, bevor die Welt untergeht, wird die
eines Experten sein, der versichert, das sei gar nicht möglich.
Philip Chee
> Manuel Reimer wrote:
>> It should be possible to do this just for "URLs" passed via command
>> line.
>
> Sorry for quoting myself ;-)
>
> It most probably *is* possible. If the default setting can be reverted
> to the old default, if command line searches *always* trigger the
> search, then I'll have a look at this, file a bug and (maybe) attach a
> patch. In my opinion searches from command line shouldn't depend on
> "keyword.enabled". Even if the user disables this, external applications
> should be able to trigger a search.
So where were you when the rest of the SeaMonkey developers were
discussing how to support Vista's method of passing search urls to a
browser and we decided to leverage on the "keyword.enabled" setting? We
didn't hear a peep out of you *then*.
Phil
--
Philip Chee <phi...@aleytys.pc.my>, <phili...@gmail.com>
http://flashblock.mozdev.org/ http://xsidebar.mozdev.org
Guard us from the she-wolf and the wolf, and guard us from the thief,
oh Night, and so be good for us to pass.
[ ]Sysop Halted... Pres F13 to continue...
* TagZilla 0.066.6
Manuel Reimer
> So where were you when the rest of the SeaMonkey developers were
> discussing how to support Vista's method of passing search urls to a
> browser and we decided to leverage on the "keyword.enabled" setting? We
> didn't hear a peep out of you *then*.
When did someone discuss this? I searched bugzilla and didn't find any
bug about this issue. Does someone have the Bug-ID.
If you discussed on IRC: Noone invited me and I can't be everywhere. The
last few weeks I had pretty much work with PrefBar as Firefox 3.0 caused
more problems as expected.
I'm not 100% sure that I'm able to catch up the command line as I just
tried some things using Venkman, but the results look nice. It *should*
be possible to catch the "open URL" event, check if the URL is valid and
trigger a search *always* independent of "keyword.enabled". This
a) makes this "Vista feature" independent of this setting. It even works
if the user disables the setting, again.
b) allowes to switch back to the old default and so make the GUI work
like in SM 1.x
Even if my "JS-Only" approach fails, someone maybe is able to tell me
where in the C-Backend the command line is parsed, so I'm able to figure
out how to change there.
I won't look deeper into this one as long as I'm unsure if a patch is of
interest.
CU
Manuel
Neil
> Even if my "JS-Only" approach fails, someone maybe is able to tell me
> where in the C-Backend the command line is parsed, so I'm able to
> figure out how to change there.
It's parsed in the same place as it is for URLs entered into the URL
bar, which is why the same pref affects both.
However in theory we could have a second preference which we would read
in the UI and if that was false we would pass a flag that temporarily
disables the first preference. See
nsIWebNavigation::LOAD_FLAGS_ALLOW_THIRD_PARTY_FIXUP (apparently
referenced six times in navigator.js).
Philip Chee
> Philip Chee wrote:
>> So where were you when the rest of the SeaMonkey developers were
>> discussing how to support Vista's method of passing search urls to a
>> browser and we decided to leverage on the "keyword.enabled" setting? We
>> didn't hear a peep out of you *then*.
>
> When did someone discuss this? I searched bugzilla and didn't find any
> bug about this issue. Does someone have the Bug-ID.
<https://bugzilla.mozilla.org/show_bug.cgi?id=408248>
"When Seamonkey is launched from the command line with 'seamonkey.exe "?
queryterm"', it throws an error message instead of launching the default
search engine and searching for 'queryterm', the expected behaviour in
Windows XP"
> If you discussed on IRC: Noone invited me and I can't be everywhere. The
There is always:
<http://www.hirsch.sth.ac.at/~robert/thebot-logs/seamonkey-index.xml>
> last few weeks I had pretty much work with PrefBar as Firefox 3.0 caused
> more problems as expected.
Yes and I had to work on Flashblock *and* Console² because almost every
new alpha/beta/rc caused more problems than expected. Especially despite
assuring us extension developers that "features are frozen it's safe to
update your extensions to Firefox 3.0", they then checked in late
breaking changes - and they did this several times too. :P
> I'm not 100% sure that I'm able to catch up the command line as I just
> tried some things using Venkman, but the results look nice. It *should*
> be possible to catch the "open URL" event, check if the URL is valid and
> trigger a search *always* independent of "keyword.enabled". This
>
> a) makes this "Vista feature" independent of this setting. It even works
> if the user disables the setting, again.
> b) allowes to switch back to the old default and so make the GUI work
> like in SM 1.x
>
> Even if my "JS-Only" approach fails, someone maybe is able to tell me
> where in the C-Backend the command line is parsed, so I'm able to figure
> out how to change there.
>
> I won't look deeper into this one as long as I'm unsure if a patch is of
> interest.
File a bug and CC the usual suspects. CC me as well please so that I can
remember to vote for it.
Phil
--
Philip Chee <phi...@aleytys.pc.my>, <phili...@gmail.com>
http://flashblock.mozdev.org/ http://xsidebar.mozdev.org
Guard us from the she-wolf and the wolf, and guard us from the thief,
oh Night, and so be good for us to pass.
[ ]If rich, eat when you please. If poor, eat when you can.
* TagZilla 0.066.6
Manuel Reimer
> However in theory we could have a second preference which we would read
> in the UI and if that was false we would pass a flag that temporarily
> disables the first preference. See
> nsIWebNavigation::LOAD_FLAGS_ALLOW_THIRD_PARTY_FIXUP (apparently
> referenced six times in navigator.js).
Thanks for answering.
What about "nsBrowserAccess.prototype" in navigator.js?
If I open a URL from command line, then Venkman tells me, that this is
called first, so if this is only used for command line (doesn't the
URL-Bar directly access tabbrowser?), then this would be the right place
to add a check, if the URL is valid. If the URL is invalid, then the
default search engine (function "OpenSearch") could be called with the
"URL" as search term.
CU
Manuel
Robert Kaiser
> IMO this should be switched back to the old behaviour, as we already
> have the "search google for" entry in our dropdown.
It's your right to have that opinion, of course, but we already have
decided the other way - at least for now. If alpha testing shows that
users have a problem with that, we can revisit this, but let's wait for
alpha feedback first before reopening each and every decision we make,
please.
Robert Kaiser
Manuel Reimer
> It's your right to have that opinion, of course, but we already have
> decided the other way - at least for now. If alpha testing shows that
> users have a problem with that, we can revisit this, but let's wait for
> alpha feedback first before reopening each and every decision we make,
> please.
It has been decided to allow searches via command line parameters, but
perhaps this is possible even without this change. I'll have a look at
that.
CU
Manuel
Manuel Reimer
> What about "nsBrowserAccess.prototype" in navigator.js?
It could do that job.
"nsBrowserAccess.prototype.openURI is called if an external app requests
a new URL to be opened.
Asking "process explorer" to search for "lsass.exe" returns a silly URL
like the following one:
http:///?%20lsass.exe
I don't know what command line switch has been used to create this URL
but stripping of the "http:///?%20" part gives me the valid search
string and allowes to call the search engine.
CU
Manuel
Benoit Renard
Will Google finally be selected as default in new profiles instead of
the useless Ask Jeeves? I know you've said several times in the past
that Google is already the default, but this is false. I installed
SeaMonkey on my WinXP laptop the day before yesterday after a "Recovery
Disc" install and Ask Jeeves was the default.
BenoitRen
Manuel Reimer
> Will Google finally be selected as default in new profiles instead of
> the useless Ask Jeeves? I know you've said several times in the past
> that Google is already the default, but this is false. I installed
> SeaMonkey on my WinXP laptop the day before yesterday after a "Recovery
> Disc" install and Ask Jeeves was the default.
Why Google? In my opinion it may be a good idea to roll out a browser
which has something else as default as "just again google". It doesn't
have to be ask.com. Yahoo may be also nice, but I don't think it
forcefully has to be google!
CU
Manuel
Manuel Reimer
> <https://bugzilla.mozilla.org/show_bug.cgi?id=408248>
Thanks. The fix for firefox is a pretty nice start. Even better as my
first idea which didn't work in some (most...) situations. I'll try to
port this over to SeaMonkey. This way the search engine setting would be
respected and there would be no longer a dependency on keyword.enabled.
CU
Manuel
Robert Kaiser
That's good, but I still want keyword.enabled to DEFAULT to on, as I've
stated multiple times in different bugs and discussions.
Robert Kaiser
Robert Kaiser
> Will Google finally be selected as default in new profiles instead of
> the useless Ask Jeeves? I know you've said several times in the past
> that Google is already the default, but this is false. I installed
> SeaMonkey on my WinXP laptop the day before yesterday after a "Recovery
> Disc" install and Ask Jeeves was the default.
From all I see and know, Google _is_ the default for en-US. But of
course, different languages can set this differently.
Robert Kaiser
Robert Kaiser
> Why Google?
Because.
Robert Kaiser
Robert Kaiser
> It has been decided to allow searches via command line parameters, but
> perhaps this is possible even without this change. I'll have a look at
> that.
It has been decided to enable the "keywords" feature by default because
we want it by default. That it solved the Vista thing was just a nice
coincidence.
Robert Kaiser
Manuel Reimer
> That's good, but I still want keyword.enabled to DEFAULT to on, as I've
> stated multiple times in different bugs and discussions.
Why? It would be OK if it would trigger the search engine the user has
selected. IMO the current behaviour is a bug by design. As long as there
is no fix available to trigger the user-selected search engine, this
should be reverted to *disabled*.
CU
Manuel
Robert Kaiser
> Robert Kaiser wrote:
>> That's good, but I still want keyword.enabled to DEFAULT to on, as
>> I've stated multiple times in different bugs and discussions.
>
> Why?
Because.
Robert "grumpy" Kaiser
Manuel Reimer
> It has been decided to enable the "keywords" feature by default because
> we want it by default. That it solved the Vista thing was just a nice
> coincidence.
The "keywords" thingy is broken by design. It triggers a search engine,
the use never selected. This is nice to have in backend, so the user,
who knows what he does, is able to enable it, but not for the regular
user who gets confused as google and not his default search engine is
triggered.
CU
Manuel
Manuel Reimer
>> Why?
> Because.
That's usually a bad way to argument in discussions ;-)
Only nice and useful changes should be added by default. The
keywords-thing at least has to be fixed to use the default search engine
as this is what users expect.
CU
Manuel
Neil
> What about "nsBrowserAccess.prototype" in navigator.js?
>
> If I open a URL from command line, then Venkman tells me, that this is
> called first, so if this is only used for command line (doesn't the
> URL-Bar directly access tabbrowser?), then this would be the right
> place to add a check, if the URL is valid.
No, it's also used for (content) window.open and <a target> links, plus
trying to open a URL directly against the nsDocLoader; either way, you
have to have already fixed up the URI by this point.
Neil
> Will Google finally be selected as default in new profiles instead of
> the useless Ask Jeeves?
It's not supposed to be the default but maybe the code that ensures the
default search engine isn't working correctly.
Robert Kaiser
> Only nice and useful changes should be added by default. The
> keywords-thing at least has to be fixed to use the default search engine
> as this is what users expect.
Actually, that might be a good idea. Can you file a bug and patch? :)
IMHO, the feature is much more nice and useful than the previous
behavior even without that, but I agree that using the default engine
would be even better.
Robert Kaiser
Manuel Reimer
> Actually, that might be a good idea. Can you file a bug and patch? :)
EXACTLY that's the point :-)
> IMHO, the feature is much more nice and useful than the previous
> behavior even without that, but I agree that using the default engine
> would be even better.
After reconsidering this topic, I agree with you. Entering something and
press enter to get www. and .com added seems to be pretty useless as
".com" gets more and more unimportant as many pages are hosted in
country specific TLDs or similar.
This feature just has to be fixed to use the selected search engine...
I'll have a look at this...
CU
Manuel
Benoit Renard
> press enter to get www. and .com added seems to be pretty useless as
> ".com" gets more and more unimportant as many pages are hosted in
> country specific TLDs or similar.
Other browers do it with a modifier key. Like Ctrl+Enter adds www. and .com.
Benoit Renard
> course, different languages can set this differently.
Broken record. :(
KaiRo, all I use /are/ en-US builds! And Google has /never/ been the
default in new profiles.
Benoit Renard
KaiRo seems to have a "Because." day today. :D
Anyway, because it was supposed to be the default. It makes sense, since
Google is the best to me and a lot of people.
Peter Potamus the Purple Hippo
it has always been in mine. Same builds.
--
*IMPORTANT*: Sorry folks, but I cannot provide email
help!!!! Emails to me may become public
Notice: This posting is protected under the Free Speech
Laws, which applies everywhere in the FREE world, except for
some strange reason, not to the mozilla.org newsgroup
servers, where your posting may get you banned.
Peter Potamus & His Magic Flying Balloon:
http://www.toonopedia.com/potamus.htm
Steve Wendt
> Other browers do it with a modifier key. Like Ctrl+Enter adds www. and
> .com.
Which always annoys me, as I want that to open the URL in a new tab!
Nelson Bolyard
> Nelson Bolyard wrote, On 2008-06-22 11:43:
>> Barry Edwin Gilmour wrote, On 2008-06-22 04:03:
>
>>> but, the old
>>> Edit/(Legacy_Prefwindow...)/(Migrated:_Browser)/Internet_Search/Default_Search_Engine/Search
>>> using:
>>> preference, gives a button with the name of the default-engine on it,
>>> and with the drop-down-menu selector, (choice of the seven
>>> search-engines I installed for-convenience into my personal-profile, as
>>> each nightly clears out the system /usr/local/sm, except-for the plugins).
>> Seven, eh? I gotta figure out how to add more. I have only 3, and it
>> doesn't matter which one I choose. Regardless of the choice, they all
>> go to google. That's got me steamed.
>
>>> Don't laugh, but I don't use Yahoo-search.
>> Neither do I, normally, but right now, I'm absolutely determined to put a
>> stop to SM's decision to send everything to google, so I've blocked access
>> to google from my local network entirely. When SM gives me back control
>> over my searches, then I'll allow the use of Google again. Not until then.
>>
>>> Three of the engines "Ask.com" "dmoz.org" and "Google",
>
> Those are the 3 engine choices I see, and it doesn't matter which I select.
> All searches go to google (or rather, it tries, but I've cut off all access
> to google at the router.)
>
> Thanks to Neil's suggestion, I unchecked the new pref
> "Perform a web search when entered text is not a web location",
> and that restored the behavior of trying www. and .com. (Thanks, Neil!)
>
> So, now the remaining problem is putting a stop to all searches going
> to google, even when I've selected Ask or dmoz.
Update: Simply unchecking the "Perform a web search when entered text is not
a web location" pref had the effect that it tried adding ".com"
before going to the search, but if that didn't work, it always searched
using google, even though I had chosen another search engine for my default.
Restarting SM seemed to fix that. Now it is honoring my pref for search
engine.
I think it's terrible that ANY pref (other than the pref for default
search engine plugin) forces all searches to go to google. That's a bug
to be fixed post haste, IMO. But I'm glad I've found a way out of it.
Nelson Bolyard
Agreed, whole heartedly.
I'm not a "regular user". I'm a module owner, and have committed over
100K lines of code. I also heavily use most SM features. Still, I find this
thing confusing and I consider it broken, just as you said.