Closed
Bug 678509
Opened 14 years ago
Closed 14 years ago
Remove showfor JS that filters searches
Categories
(support.mozilla.org :: Knowledge Base Software, task)
support.mozilla.org
Knowledge Base Software
Tracking
(Not tracked)
VERIFIED
FIXED
2011-08-30
People
(Reporter: jsocol, Assigned: rrosario)
References
Details
The showfor search JS sets search forms to look for the current os/fx combination right now. We need to remove that and should just put the correct product tag(s) filter into the search form on each landing page.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → rrosario
Assignee | ||
Comment 1•14 years ago
|
||
If we filter by product based on OS selected, then we will never be searching for sync and fxhome articles on pages that have showfor selector. Is that ok?
Reporter | ||
Comment 2•14 years ago
|
||
We shouldn't change the product based on the OS selected.
On the /home page, we should filter by, e.g. 'desktop' and 'sync' tags, on /mobile, 'mobile' and 'sync', on /fxhome, 'FxHome' and 'sync', etc. The showfor JS doesn't need to change this filter anymore, since showfor is not becoming product-oriented.
Assignee | ||
Comment 3•14 years ago
|
||
oh yeah, that makes sense!
Assignee | ||
Comment 4•14 years ago
|
||
(In reply to James Socol [:jsocol, :james] from comment #2)
> On the /home page, we should filter by, e.g. 'desktop' and 'sync' tags, on
> /mobile, 'mobile' and 'sync', on /fxhome, 'FxHome' and 'sync', etc.
We already filter articles and questions tagged 'mobile' when searching from /mobile. I will spin off the others as a separate bug that gets fixed once most of the articles have been tagged appropriately. This way we don't get empty search results in the meantime.
Assignee | ||
Comment 5•14 years ago
|
||
Removed the js that adds os and fx params to search from the landing pages:
https://github.com/jsocol/kitsune/commit/57572301247f7f2c52016dc3c3ad57238bafb94f
Filed Bug 680480 for adding filtering based on landing page product.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 7•14 years ago
|
||
Verified with Firebug that no hidden input fields are in the DOM after doing a search, especially not those that are type=hidden.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•