1053893 - [UX] mockup for selected search engine prompt

Status: RESOLVED FIXED

(Firefox :: Search, defect)

Description

[:Gavin Sharp [email: [e-mail]]]

See details in bug 1029725 and https://wiki.mozilla.org/User:Mconnor/Search_API_Change#UI_Treatment . We should get a finalized mockup from UX, and ideally any assets (if required).

Comment 1

[:Gavin Sharp [email: [e-mail]]]

Sevaan, what's the status here? I forgot to flag this one as one whose strings we'd like to get in as soon as possible - can we get a quick turnaround on the text?

Comment 2

[Sevaan Franks [:sevaan]]

(In reply to :Gavin Sharp [email: [e-mail]] from comment #1)
> Sevaan, what's the status here? I forgot to flag this one as one whose
> strings we'd like to get in as soon as possible - can we get a quick
> turnaround on the text?

Hey :Gavin. I just worked on this on the plane back home and was waiting to review with :phlsa.

A little explanation first, since the vehicle for notifying the user is different than what :mconnor proposed...

We have a few ways of notifying users: Modals, Notification Bars, and Doorhangers.

Modals are reserved for show-stopper decisions, because it interrupts browsing and any other functions of Firefox until the user makes a choice. "You can go no further until you deal with this right this moment" (one of the reasons we are no longer using a modal for asking users if they want Firefox as their default browser).

Notification Bars are "Hey, you need to make a decision here, but you can keep surfing, and you can deal with this when you are ready...or if you don't deal with it, nothing will change."

Doorhangers are for the lowest level of notification as they are a bit more fleeting.

So, in discussing with :phlsa, we feel that a global notification bar across tabs would best serve the purpose of notifying users about potential search engine changes. It would allow the user to keep surfing, but would remain at the top of the screen until it is dealt with. Or, if a user closes the browser without making a choice, no change would be made.

A mockup of the notification bar is attached.

It's basic at the moment and fulfills the functionality of this bug. However, :mmaslaney is working on a bug to redesign all the notification bars, at which time will want to include the search engine favicons to give the additional visual cue to the user. They just don't fit at the moment without us creating a custom bar or custom buttons for this specific bar.

Comment 3

[Sevaan Franks [:sevaan]]

Attachment: Switch Search Provider Alert Notification Bar

Comment 4

[Sevaan Franks [:sevaan]]

Matej:

We are creating a notification bar to alert users if an add-on is going to change their default search provider. What are your thoughts on this string?:

"<NAME OF ADD-ON> wants to change your search provider to <NEW PROVIDER>. Learn more."
Button 1: "Switch to <NEW PROVIDER>"
Button 2: "Keep searching with <CURRENT PROVIDER>"

Comment 5

[Matej Novak [:matej]]

(In reply to Sevaan Franks [:sevaan] from comment #4)
> Matej:
> 
> We are creating a notification bar to alert users if an add-on is going to
> change their default search provider. What are your thoughts on this string?:
> 
> "<NAME OF ADD-ON> wants to change your search provider to <NEW PROVIDER>.
> Learn more."
> Button 1: "Switch to <NEW PROVIDER>"
> Button 2: "Keep searching with <CURRENT PROVIDER>"

Looks good, just wondering about "search provider" vs. "search engine."

Comment 6

[Sevaan Franks [:sevaan]]

I think search engine is probably more the more common expression. Let's use that.

Thanks Matej!

Comment 7

[Sevaan Franks [:sevaan]]

Attachment: Switch Search Engine Alert Notification Bar

Comment 8

[:Gavin Sharp [email: [e-mail]]]

Perhaps the context here wasn't clear enough. In theory an add-on could call this API while a non-browser window is open, in which case it would be awkward to show a notification bar. I think the idea was that this is only intended to be called in response to a user action (e.g. clicking an add-on's "Add our search engine" button), which also changes things.

Comment 9

[Mike Connor [:mconnor]]

or it could be a first run thing after an add-on install, etc.  It doesn't need to be _modal_, per se, but it should be something that allows us to have a clear and unambiguous UI.  Given that we're going to force add-ons down this path I think we should find more of a middle ground (perhaps with the ability to have a blurb/visuals describing the switch).

Given that, and Gavin's point, I don't think tab-modal notification fits, since it's probably not relevant to a single tab.

Finally, yellow is misplaced, if it's a notification bar it should be an info type, not a warning.

Reopening until we've got something that better fits the use-case we're considering.

Comment 10

[Marco Mucci [:MarcoM]]

Filed Bug 1066739 for new designs/revisions.