Bug 852376 - The value of searching options will return to the keywords field after searching.
Summary: The value of searching options will return to the keywords field after search...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OKD
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Clayton Coleman
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-28 10:00 UTC by Yujie Zhang
Modified: 2015-05-15 01:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-11 16:15:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot1 (11.41 KB, image/png)
2012-08-28 10:00 UTC, Yujie Zhang
no flags Details

Description Yujie Zhang 2012-08-28 10:00:54 UTC
Created attachment 607463 [details]
screenshot1

Description of problem:

After I input the searching keywords, I selected the content type, and click the "Advanced Search" button, it will return the searching result, but the value of content type will return to the keywords field too, do not think this is expected.

Version-Release number of selected component (if applicable):

devenv_2085

How reproducible:always


Steps to Reproduce:
1.Go to openshift website
2.Input the search keyword 
3.Select the content type on advanced search page and click the "Advanced Search" button
  
Actual results:

The value of search options will return to the keywords field.Details see in attachment please.

Expected results:

The value of search options should not return to the keywords field.

Additional info:

Comment 1 Steve Goodwin 2012-09-11 15:54:27 UTC
Listing both the keyword(s) along with any specific content parameters and/or search operators in the main search input field, is a valid way (Google does this) to denote the search results listed are restricted to those criteria. 

Though there are other ways to display this to the user, the development resources are better spent on higher priority bugs.

Comment 2 Clayton Coleman 2012-09-11 16:15:10 UTC
Not going to fix, working as designed.  Search is something we get for free from Drupal and like steve says we're not going to have the time to devote to its improvement.


Note You need to log in before you can comment on or make changes to this bug.