Closed
Bug 246530
Opened 20 years ago
Closed 16 years ago
keywords don't work if they contain a period
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: mikel, Unassigned)
Details
The internet keywords information page <http://www.mozilla.org/docs/end-user/internet-keywords.html> suggests that any string consisting of multiple whitespace separated words or any single word that is not a valid URL will be handled by the internet keywords system. This sounds very useful, and is what I had enabled using the prefs UI. If I enter a search term containing a period (.) such as "mozilla user.js" and press enter I get an alert dialog with the following text: "The URL is not valid and cannot be loaded" I would really like this to cause a keyword search as the documentation leads me to believe. I also can't think of a situation where a valid URL could contain literal whitespace (it would have to be % escaped), so it shouldn't be ambiguous as far as I can see. Currently using Mozilla Seamonkey 1.6 (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510).
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 1•16 years ago
|
||
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.13) Gecko/20060414] (release) (W2Ksp4) Confirming, on Windows, with |keyword.enabled = true|. *** [Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9] (release) (W2Ksp4) WorksForMe, with |keyword.enabled = true|. *** [Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.15pre) Gecko/2008060503 BonEcho/2.0.0.15pre] (nightly) (W2Ksp4) [Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9pre) Gecko/2008060507 Minefield/3.0pre] (nightly) (W2Ksp4) [Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9pre) Gecko/2008060802 SeaMonkey/2.0a1pre] (nightly) (W2Ksp4) WorksForMe, by default.
Severity: normal → minor
Status: NEW → RESOLVED
Closed: 16 years ago
OS: Linux → All
Resolution: --- → WORKSFORME
Version: 1.4 Branch → 1.7 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•