175419 - clicking a bookmark with %s (custom keyword query) should ask for parameter

Status: RESOLVED EXPIRED

(SeaMonkey :: Bookmarks & History, enhancement)

Description

[Vaclav Dvorak]

When you file a bookmark where the URL contains %s (and, presumably, assign a
keyword for it), it appears among the other bookmarks without any distinction.
Clicking it in the bookmarks menu goes to the URL as specified, including the
%s. That's almost certainly not a valid URL and what the user wanted. I propose
that a dialog should pop up in this case, asking for the parameter(s) to be used
in place of the %s('s).

[We might also consider doing the same for links in documents: a web page author
might put <a href="http://www.google.com/search?q=%s">click this to search
Google</a> in his HTML and thus enable his Mozilla-using visitors with a Google
search (or something less widely known).]

If this will be wontfix, I propose reopening bug 162777.

Comment 1

[Nathan Kurz]

I agree this is a problem, and like the solution presented.  This would
definitely be an enhancement, though.  

Another way of solving the problem would be to always substitute for "%s", using
an empty string if no argument is present.  With many searches, this will at
least take to you the correct page so you can enter the arguments into the
search form.  But I'm sure there is some user somewhere who really needs a "%s"
in their bookmark. And both of these solutions would mess that up.  

Personally, I've been thinking of trying out an extension to the bookmarks that
would add a whole slough of "arguments" options:  drag-and-drop arguments,
arguments from current selection, the popup dialogue mentioned here, and a
slough of corresponding preferences on a separate panel on Bookmark Properties.

Comment 2

[Michael Lefevre]

sounds like a reasonable RFE. confirming.

Comment 3

[Jesse Ruderman]

Bug 253457 is the same bug for Firefox.

Comment 4

[Robert Kaiser]

MASS-CHANGE:
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

Comment 5

[Robert Kaiser]

MASS-CHANGE:
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

Comment 6

[Robert Kaiser]

MASS-CHANGE:
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

Comment 7

[Robert Kaiser]

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