759551 - Inline search for mobile

Status: RESOLVED DUPLICATE of bug 790066

(Marketplace Graveyard :: Consumer Pages, defect, P3)

Description

[Gregory Koberger (:gkoberger)]

We need inline search for mobile:

* Hide the search box; add a finder icon.
* When opened, there should be a white overlay over the whole page that's filled with search suggestions as the user types.
* Maybe make the finder icon a heavily styled input that changes on focus, so the user only has to click once? (some mobile browsers don't allow .focus on elements)

Comment 1

[Christopher Van Wiemeersch [:cvan]]

What we currently have:
- http://cl.ly/2i061z1u152Y3O3s2t0f

What we could potentially have:
- http://i.imgur.com/Ozm1Z.png
- http://i.imgur.com/l6ItJ.png

A few things worth mentioning:
1) In an early attempt to make this all work, I made this the magnifying glass: http://i.imgur.com/reayT.png Upon click it exposed the search box.
2) We should try to see if we can merge the header and breadcrumbs on mobile (à la http://i.imgur.com/wEz35.png but hopefully slicker).
3) The Marketplace icon should be larger, as it's way, way too small on mobile (bug 759960).
4) Relevant to the header UI: there is some discussion in bug 759553 about the header nav icon (http://cl.ly/0f1j3T0m2t0m3R0Q3T2O) — a thing that is a UI pattern within Fennec, Browser w/in B2G's Gaia, Facebook's apps, etc.). How that integrates with search in our header can be addressed in this bug.

Comment 2

[Wil Clouser [:clouserw]]

I feel like this is getting trumped by things like bug 766879 but willing to triage it with maria so I'll leave it open

Comment 3

[Maria Sandberg [:mushi]]

Is this covered by the following (from bug 766879 comment 3) or do you need more detail on the search suggestion behavior?

2.  Clicking the search button turns the top bar into a search field, in focus and brings up the keyboard. See (https://wiki.mozilla.org/File:Gaia_BB_ContactsBrowser_1.png) for the B2G pattern for this.

Comment 4

[Christopher Van Wiemeersch [:cvan]]

(In reply to msandberg from comment #3)
> Is this covered by the following (from bug 766879 comment 3) or do you need
> more detail on the search suggestion behavior?

So should we start showing text-only search suggestions upon keypresses? Or should we start showing the full search view?

Comment 5

[Christopher Van Wiemeersch [:cvan]]

(In reply to Chris Van Wiemeersch [:cvan] from comment #4)
> (In reply to msandberg from comment #3)
> > Is this covered by the following (from bug 766879 comment 3) or do you need
> > more detail on the search suggestion behavior?
> 
> So should we start showing text-only search suggestions upon keypresses? Or
> should we start showing the full search view?

Maria, what are your thoughts here?

Comment 6

[Maria Sandberg [:mushi]]

(In reply to Chris Van Wiemeersch [:cvan] from comment #5)
> (In reply to Chris Van Wiemeersch [:cvan] from comment #4)
> > (In reply to msandberg from comment #3)
> > > Is this covered by the following (from bug 766879 comment 3) or do you need
> > > more detail on the search suggestion behavior?
> > 
> > So should we start showing text-only search suggestions upon keypresses? Or
> > should we start showing the full search view?
> 
> Maria, what are your thoughts here?

When a user clicks the search button (or the search bar if on for example a results page) we bring up the keyboard and turn the top bar into a search field (b2g pattern). 

When a user starts typing (after first keypress), we start showing text-only search suggestions if we have them. How are those generated?

Comment 7

[Christopher Van Wiemeersch [:cvan]]

Davor probably wants this.

Comment 8

[Christopher Van Wiemeersch [:cvan]]

Forward duping.