Closed Bug 81643 Opened 23 years ago Closed 22 years ago

multi-engine(aggregate) search not working with relative URLs

Categories

(SeaMonkey :: Search, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 65453
Future

People

(Reporter: lynnw, Assigned: samir_bugzilla)

Details

(Keywords: helpwanted, intl)

If a user performs a multi-engine (or aggregate) search and then elects to view 
all of the results from one of the search engines by clicking on the search 
engine button above the results in the main browser window, the user is taken to 
that search engine's search result page. However, if the search engine provider 
uses relative links for their search results, the links change to 
"chrome://communicator/..." instead of "http://....".
This was seen in 20010511.
Keywords: intl, rtm
nav triage team:

Removing nsrtm keyword, multi-engine search is not a rtm stop ship. Marking p3,
mozilla1.2, and adding helpwanted keyword. Adding jaimejr to cc-list
Keywords: nsrtmhelpwanted
Priority: -- → P3
Target Milestone: --- → mozilla1.2
nav triage team:

Forgot nsbeta1+
Keywords: nsbeta1+
moz 1.2? musta got lost
Assignee: matt → sgehani
CLaudius, 
Is this a problem for any engines we ship?
Target Milestone: mozilla1.2 → Future
Is the problem described in bug 65453 the same issue?
Ok, dupe. The other bug has 5 votes.

*** This bug has been marked as a duplicate of 65453 ***
Status: NEW → RESOLVED
Closed: 22 years ago
OS: Windows NT → All
Hardware: PC → All
Resolution: --- → DUPLICATE
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.