Search by specific url (e.g. url:youtube.com) not implemented

RESOLVED WONTFIX

Status

P3
enhancement
RESOLVED WONTFIX
8 years ago
6 years ago

People

(Reporter: stephend, Unassigned)

Tracking

Trunk
Future

Details

(URL)

(Reporter)

Description

8 years ago
STR:

1. Load http://m.input.stage.mozilla.com/en-US/search/?product=mobile&q=twitter
2. Notice there are feedback results (2, currently) for "twitter.com"
3. Now, do a search for "url:twitter.com" (http://m.input.stage.mozilla.com/en-US/search/?product=mobile&q=url%3Atwitter.com)

Expected:

Should find the above two URLs

Actual:

No search results found
Flags: in-litmus?
Dave, will you check mobile search works like desktop?
Assignee: nobody → dd
I didn't think we supported url:yoursite.com yet only url:*
(Reporter)

Comment 3

8 years ago
(In reply to comment #2)
> I didn't think we supported url:yoursite.com yet only url:*

http://input.mozilla.com/en-US/search/?product=firefox&q=url%3Amozilla.com

So, we differ on Mobile vs. Desktop
> http://input.mozilla.com/en-US/search/?product=firefox&q=url%3Amozilla.com
> 
> So, we differ on Mobile vs. Desktop

How is that different than:
http://m.input.mozilla.com/en-US/search/?product=firefox&q=url%3Amozilla.com

It's matching on url mozilla.com being in the opinion.  It's not a filter in this case.

Rewording this bug.
Severity: major → enhancement
Summary: Mobile - URL searching is broken (url:twitter.com) → Search by specific url (e.g. url:youtube.com) not implemented
(Reporter)

Comment 5

8 years ago
Don't think this is an "enhancement"; load http://m.input.mozilla.com/en-US/#trends and click on any of those sites below, and you'll see "url:youtube.com", for example:

http://m.input.mozilla.com/en-US/search/?q=url%3Ayoutube.com&product=mobile&version=4.0b1
The summary of this bug is to give users the ability to search by specific urls. Our current implementation doesn't do this. I'd go as to say that the current implementation is just half done in the eyes of any person checking out this dashboard. 

You can make an argument in both respects, so I don't care about the severity much. I'll just care if this isn't fixed for 2.0 to the expectation of what Stephen reported with this bug.
Target Milestone: 2.0 → 2.1
Priority: -- → P3
Target Milestone: 2.1 → 3.0
Target Milestone: 3.0 → 3.2

Updated

8 years ago
Target Milestone: 3.2 → 3.3
Target Milestone: 3.3 → 4.1
Moving things dependent on ES to FUTURE.
Depends on: 627568
Target Milestone: 4.1 → Future
(Assignee)

Updated

7 years ago
Component: Input → General
Product: Webtools → Input
Assignee: dd → nobody
I don't think this is relevant to the new Input. Marking as WONTFIX.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.