831910 - Story - Use the Auto-Complete Screen

Status: RESOLVED FIXED

(Tracking Graveyard :: Metro Operations, defect, P1)

Description

[Asa Dotzler [:asa]]

Attachment: UC-39 Use the auto-complete screen

Comment 2

[Asa Dotzler [:asa]]

Attachment: Use the auto-complete screen's auto-complete tiles

Updated story.

Comment 3

[Brian R. Bondy [:bbondy]]

This can be reduced to a p=2 if we create a new story which is low priority for bug 784042.

Comment 4

[Marco Mucci [:MarcoM]]

New story would have Bug 784042 as its work dependency.

Comment 5

[Asa Dotzler [:asa]]

That sounds fine to me. Marco, can you create that story bug or do you need me to?

Comment 6

[Marco Mucci [:MarcoM]]

Hi Asa, I'll create the shell and move it to 'on hold' where you can review and add details.

Comment 7

[Allison Naaktgeboren :ally]

Note, this does not include the snapped view autocomplete work: that is story 833200

Comment 8

[Yuan Wang(:Yuan) – Mobile Firefox Design Lead]

Attachment: Proposed solution for auto-complete screen

Frank, Stephen, and I agreed upon this solution (please see attached pdf).
 
The behaviors: 
Tapping on URL field triggers a search app bar which only contains a search field, a Close button. (Start Page will not be shown in this case)

When the user starts typing, results show up on a semi-transparent in-context auto-complete page.

To exit, tap the “Close” button on the bottom right.

Still awaiting for feedback from Asa. But I will start prototyping transitions anyway.

Comment 9

[Allison Naaktgeboren :ally]

:mbrubeck has requested this one as his start bugs touch this heavily.

Comment 10

[Matt Brubeck (:mbrubeck)]

(In reply to Yuan Wang(:Yuan) – Firefox UX Team from comment #8)
> When the user starts typing, results show up on a semi-transparent
> in-context auto-complete page.

Any particular requests for the autocomplete results in snapped mode?  Should they be half-height like the new full view, or full-height like they are now?

Comment 11

[Yuan Wang(:Yuan) – Mobile Firefox Design Lead]

(In reply to Matt Brubeck (:mbrubeck) from comment #10)
> (In reply to Yuan Wang(:Yuan) – Firefox UX Team from comment #8)
> > When the user starts typing, results show up on a semi-transparent
> > in-context auto-complete page.
> 
> Any particular requests for the autocomplete results in snapped mode? 
> Should they be half-height like the new full view, or full-height like they
> are now?

I think it makes more sense to have the snap view auto-complete half-height like the new full view. So when the users change Firefox from full to snap view(or vice versa), the transitions will feel natural. Also, half-height screen is friendly for soft keyboard users. 

The only question is if we can display 9 search result tiles, and 6 small search engine tiles. If not, we will need to cut the number of search results.

Stephen, could you play around with the new tiles (probably smaller version) and see how well they can fit in the half-height snap view? Thanks!

Comment 12

[Stephen Horlander [:shorlander]]

Here are some explorations around this: http://people.mozilla.com/~shorlander/files/design-specs-metro/metro-designSpecs-awesomeResults-splitView.html

If we want to use a partial overlay then the tiles will have to be pretty small and the search options will be cut off with the onscreen keyboard.

We can show fewer results and scroll the search engines or we can use a full width/height overlay and show larger tiles and scroll all of it for onscreen keyboard use.

Comment 13

[Yuan Wang(:Yuan) – Mobile Firefox Design Lead]

(In reply to Stephen Horlander from comment #12)
> Here are some explorations around this:
> http://people.mozilla.com/~shorlander/files/design-specs-metro/metro-
> designSpecs-awesomeResults-splitView.html
> 
> If we want to use a partial overlay then the tiles will have to be pretty
> small and the search options will be cut off with the onscreen keyboard.
> 
> We can show fewer results and scroll the search engines or we can use a full
> width/height overlay and show larger tiles and scroll all of it for onscreen
> keyboard use.

Thank you, Stephen. Those explorations are great. 
Seems like we have to cut the title and URLs if we want to use smaller tiles on partial overlay. That makes it difficult to recognize those tiles. Having a vertical scroll bar on half-screen overlay feels heavy

Being able to identify tiles are more important than consistency here. So I personally think we should go for having larger tiles on full height overlay, and enable vertical scrolling when onscreen keyboard is in use. 

Other thoughts?

Comment 14

[Matt Brubeck (:mbrubeck)]

Marco, since the UX has changed here from the design that jwilde had implemented, I'd like to change the point estimate to p=5.

Comment 15

[Marco Mucci [:MarcoM]]

Done.  Thanks Matt.

Comment 16

[Cornel Ionce [:noni] [Hubs QA]]

Mozilla/5.0 (Windows NT 6.2; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0
Build ID: 20131117030203

Covered the user story and ran through all of its scenarios without any issues using metro full view.

The only thing I would like to mention here is the close button (X). I think it's too bright, it can be quite difficult to spot it.


This also needs device verification.

Comment 17

[Kamil Jozwiak [:kjozwiak]]

Bug # 904998 was created to address the issue Cornel mentioned above regarding the "X" being too bright under the auto-complete window.