Open Bug 1330462 Opened 8 years ago Updated 2 years ago

Using a different search engine to search for the same thing one just searched for is painful

Categories

(Firefox :: Address Bar, defect, P3)

53 Branch
defect
Points:
5

Tracking

()

Tracking Status
firefox53 --- affected

People

(Reporter: dthayer, Unassigned)

References

Details

(Keywords: blocked-ux, papercut, Whiteboard: [fxsearch][fce-active-legacy][snt-write-proposal][snt-scrubbed])

Attachments

(1 file)

Steps: - Search for "corgis" with Google as default search engine - Land on a search page like this: https://www.google.com/search?q=corgis&ie=utf-8&oe=utf-8 - Click on awesome bar, hit the down key to show suggestions and other search engines - Select Yahoo - Notice that we're at https://search.yahoo.com/yhs/search?p=https%3A%2F%2Fwww.google.com%2Fsearch%3Fq%3Dcorgis%26ie%3Dutf-8%26oe%3Dutf-8&ei=UTF-8&hspart=mozilla&hsimp=yhs-002 (i.e., we searched Yahoo for the Google URL) Expected results: we should instead end up at https://search.yahoo.com/yhs/search?p=corgis&ei=UTF-8&hspart=mozilla&hsimp=yhs-002 (a Yahoo search for corgis). We could implement this by either trying to parse searches that look like URLs to find the inner query, or by just remembering that we just searched for "corgis" through the awesome bar. The former option would probably be better for a user, since if they landed on that URL through some means other than the awesome bar, they could quickly get to another search engine that they prefer. We could also display a little "Did you mean to search for http://etc..." notification, in case the user really did want to search Yahoo for the Google URL, but I think that's so unlikely that we should just let them manually enter it into the search bar directly in Yahoo.
Summary: Using a different search engine to search for the same thing I just searched for is painful → Using a different search engine to search for the same thing one just searched for is painful
moving to location bar. It's clearly a valid enhancement.
Component: Search → Location Bar
Priority: -- → P3
Whiteboard: [fxsearch]
Assignee: nobody → dothayer
Attachment #8826757 - Flags: review?(adw)
Whiteboard: [fxsearch] → [fxsearch][fce-active]
Hey Marco, who do you think I should request review from for this?
Flags: needinfo?(mak77)
(In reply to Doug Thayer [:dthayer] from comment #0) > We could implement this by either trying to parse searches that look like > URLs to find the inner query, or by just remembering that we just searched > for "corgis" through the awesome bar. The former option would probably be > better for a user, since if they landed on that URL through some means other > than the awesome bar, they could quickly get to another search engine that > they prefer. > > We could also display a little "Did you mean to search for http://etc..." > notification, in case the user really did want to search Yahoo for the > Google URL, but I think that's so unlikely that we should just let them > manually enter it into the search bar directly in Yahoo. This is a pretty much welcome feature imo, since we also discussed it earlier. I agree that searching for a url is not common, and we should not optimize for it, if the current visit came from a search, clicking on a one-off should search for the same word. Thus I'd say we should not provide that notification. The problems I see here, are mostly UX, for example when hovering the one-off buttons, we should probably temporarily show the search text in the urlbar, rather than the previous url. That may help clarifying what happens when you confirm the action, otherwise it may be surprising. Thus, you will likely need some hint from UX, I'm pinging :phlsa for that (feel free to forward if needed). Regarding the reviewer, you picked properly, no reasons to look further.
Flags: needinfo?(mak77) → needinfo?(philipp)
Blocks: 1337003
Priority: P3 → P2
Whiteboard: [fxsearch][fce-active] → [fxsearch][fce-active-legacy]
Assignee: dothayer → nobody

Clearing needinfo as Phlsa is no longer at Mozilla

Flags: needinfo?(philipp)
Priority: P2 → P3
Comment on attachment 8826757 [details] Bug 1330462 - Using a different search engine to search for the same thing one just searched for is painful This patch is too old at this point.
Attachment #8826757 - Flags: review?(adw)
Keywords: papercut
Points: --- → 5
Depends on: 1633335
Keywords: blocked-ux
Whiteboard: [fxsearch][fce-active-legacy] → [fxsearch][fce-active-legacy][snt-write-proposal]
Whiteboard: [fxsearch][fce-active-legacy][snt-write-proposal] → [fxsearch][fce-active-legacy][snt-write-proposal][snt-triaged]
Whiteboard: [fxsearch][fce-active-legacy][snt-write-proposal][snt-triaged] → [fxsearch][fce-active-legacy][snt-write-proposal][snt-scrubbed]
Severity: normal → S3

We're experimenting with persisting the search term for default search engine result pages in the urlbar via Bug 1797754.

This is enabled in Nightly and early Beta. It can also be enabled in Release in about:config:
browser.urlbar.showSearchTerms.featureGate: true
browser.urlbar.showSearchTerms.enabled: true

While this feature is enabled, you should be able to select a one-off button while on a default search engine results page and it'll reuse the search term.

Duplicate of this bug: 1633335
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: