Closed Bug 521120 Opened 15 years ago Closed 15 years ago

Search button that cuts off looks broken, and user unable to scroll thru the list

Categories

(Firefox for Android Graveyard :: General, defect, P2)

defect

Tracking

(fennec1.0+)

VERIFIED FIXED
fennec1.0b5
Tracking Status
fennec 1.0+ ---

People

(Reporter: madhava, Assigned: mfinkle)

Details

(Whiteboard: [polish])

Attachments

(5 files, 1 obsolete file)

As shown here: http://www.flickr.com/photos/madhava_work/3990228651/

The last of the default bookmark set is cut off at the edge of the screen (and will only be more so when we get the larger search provider icons in).

One possible issue is that the button cuts off before the screen edge, making it look like the end is just missing, rather than being off-screen.

What would make the intended behavior even more clear, though, is to include an overlay at the end with an arrow on it, to indicate that panning to the right is something that can be done -- this was in the original mockups and, I think, in an earlier version of the awesomescreen styling.

I'll put together a mockup and attach it to the bug.
tracking-fennec: --- → ?
Whiteboard: [polish]
Priority: -- → P2
All we need is an ability to scroll right and left on the search plugin list. 
Just like the Firefox Tabbar right/left scroll buttons.
OS: Mac OS X → All
Hardware: x86 → All
Summary: Search button that cuts off looks broken → Search button that cuts off looks broken, and user unable to scroll thru the list
(In reply to comment #1)
> All we need is an ability to scroll right and left on the search plugin list. 
> Just like the Firefox Tabbar right/left scroll buttons.

We can already pan left and right in the list. This bug is about the appearance.
Attached image screenshot
I have a crazy idea - mainly because I dislike the idea of panning left/right to get the right search engine.

Why don't we get rid of the bottom panel on the awesome screen?
Yeah crazy!

Here the idea:
 * Users need the search engines only when they want to initiate a search, which means he search for something that they wrote into the awesome bar, so why not display the search engines as _additional_ results at the end of the search?

Benefits:
 * More space on the awesome screen
 * No more pan left/right, all the search engines can fit on the screen
 * Reduce the delay the first time we show the awesomescreen by creating the rows only once the user has start a search

Here a screenshot of a very dirty implementation of the idea.
Attached patch patch (obsolete) — Splinter Review
Styles the autorepeat buttons in the autoscrollbox
Assignee: madhava → mark.finkle
Attached patch patch 2Splinter Review
This patch is the same as the last but forces the arrows to create a padding,
even when the XBL tries to collapse them
Attachment #407444 - Attachment is obsolete: true
Attachment #407641 - Flags: review?(gavin.sharp)
tracking-fennec: ? → 1.0+
Getting final images from sean.
Attached image Arrow Left - 16x24
Attached image Arrow Right - 16x24
Comment on attachment 407641 [details] [diff] [review]
patch 2

>diff --git a/themes/hildon/browser.css b/themes/hildon/browser.css

>+#autocomplete_navbuttons autorepeatbutton[disabled="true"] {
>+  visibility: hidden;

I understand the collapsed=true case, but why is this one needed? I couldn't find where the [disabled] implied a non-default visibility...

Kinda seems like whether the arrows get collapsed should be controllable with just an attribute on the scrollbox, but this is fine for now.
Attachment #407641 - Flags: review?(gavin.sharp) → review+
(In reply to comment #9)

> >+#autocomplete_navbuttons autorepeatbutton[disabled="true"] {
> >+  visibility: hidden;
> 
> I understand the collapsed=true case, but why is this one needed? I couldn't
> find where the [disabled] implied a non-default visibility...

When the scrollbox has reached one of it's extremes, the arrow is shown in a disabled state, not surprising, but looked odd in our case, so I just made the arrow disappear.
Attached file All Arrows - 16x16
updated arrows and pushed:
https://hg.mozilla.org/mobile-browser/rev/d3b74551beb2
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → B5
verified FIXED on builds:

Mozilla/5.0 (X11; U; Linux armv7l; en-US; rv:1.9.2b1pre) Gecko/20091026
Fennec/1.0b5pre

and

Mozilla/5.0 (X11; U; Linux armv6l; en-US; rv:1.9.3a1pre) Gecko/20091026
Fennec/1.0b5pre
Status: RESOLVED → VERIFIED
Flags: in-litmus?
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: