Closed Bug 65863 Opened 24 years ago Closed 14 years ago

Search Panel: clicking on a link in the results updates the results themselves

Categories

(SeaMonkey :: Search, defect)

x86
Other
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: Erich.Iseli, Unassigned)

References

(Blocks 1 open bug)

Details

It's quite hard to find a summary that describes this problems in a few words.
So let's go through it quietly.

When you perform a search, either from the sidebar or from a search engine whose
URL is recognized by a sherlock plugin, you get the results both in the sidebar
and in the browser window. This is a feature. And it's cool.

Now take the following situation: on some websites, the URL for the search and
the URL for the found pages is identical. Only difference would be the query
after the question mark. Example:

For searches: http://somesite.com/do?what=search&q=whatever
For the pages: http://somesite.com/do?what=display&page=any_page

I don't want to judge such practice, I just know there are plenty of them out
there and it would be sad if the goal of the search panel would be defeated in
these cases.

Because the goal is to have the results always visible in the sidebar while
looking for the different pages matched by the search. If the sidebar always
updates, you don't have a chance to use the sidebar.

To come back to my above example, the sherlock plugin will have <SEARCH
action="http://somesite.com/do"> which will match for both the searches and the
pages, and therefore updating the search panel results.

To fix this bug:

I suggest that we make a difference between
- a search result page loaded by submission or by entering its URL (which will
  update the search panel) on the one side
- a "search result" page loaded by clicking inside the search panel (which
  should NOT update the search panel)

Possible problem:
Search engines with both categories. If you click on a category, the expected
result is that you go one level deeper in this category. The search panel should
reflect these changes. But this is not really a problem since the categories are
recognized as categories and not as usual pages. Because of this, I would
reformulate the second item above to:

- a "search result" page loaded by clicking inside the search panel should NOT
  update the search panel, EXCEPT if the clicked item was a category, in which
  case it should update.

Any comments and suggestions welcome.

Almost forgot: if you are looking for an example, try the dictionary.com or the
thesaurus.com plugins from http://sherlock.mozdev.org/download.html
can we get some more information (precise steps) about how to repro this and
expected vs. actual results? thanks.
Assignee: matt → sgehani
Target Milestone: --- → Future
An excellent testcase would be zdnet downloads:
http://downloads-zdnet.com.com/3150-2029-0.html. Every category and subcategory
has a different html file 3150-2069-0.html, 2001-2049-0.html etc... Here, the
regular expressions would be needed to match in the "alsomatch" attribute.
Otherwise you would end with hundreds of "alsomatch" URLs. Also consider that
for all of these variations, you can have several "branded" zdnet "resellers"
like netscape, where the URL changes in
http://netscape.com.com/2001-2025-0.html. And I guess there are many more brandings.
Please ignore my comment#2, it was meant for bug 86433.
Depends on: 172122
Blocks: 172122
No longer depends on: 172122
Product: Core → SeaMonkey
Assignee: samir_bugzilla → nobody
QA Contact: claudius → search
Target Milestone: Future → ---
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.