The default bug view has changed. See this FAQ.

Change Settings > Help & Feedback feedback links

VERIFIED FIXED

Status

Firefox OS
Gaia::Settings
P2
normal
VERIFIED FIXED
5 years ago
4 years ago

People

(Reporter: Cww, Assigned: Margaret)

Tracking

({late-l10n})

unspecified
Other
Gonk (Firefox OS)
late-l10n

Firefox Tracking Flags

(blocking-basecamp:+)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
The feedback link is:

http://input.mozilla.org/feedback

We'll be updating that link in the coming weeks to be a B2G friendly site for giving feedback and maintaining that link going forward in the Input 2.0 rewrite.

The current directive to call us should be removed.

Proposed text (CCing Larissa for comments):

Give us feedback: http://input.mozilla.org/feedback

or (preferred) to have just a button that says [GIVE MOZILLA FEEDBACK] or something like that which takes you to the above link.

Comment 1

5 years ago
(In reply to [:Cww] from comment #0)
> The feedback link is:
> 
> http://input.mozilla.org/feedback
> 
> We'll be updating that link in the coming weeks to be a B2G friendly site
> for giving feedback and maintaining that link going forward in the Input 2.0
> rewrite.

Just to make sure, you'd like us to remove the first link that says "Online support" and replace it with the "Give Mozilla Feedback" button, right? We talked about a couple of ideas yesterday for a feedback app so I wanted to double-check.

If it's a feedback button only, does it make sense to add it to Settings > Device > Help Make Firefox OS better? If we do this, then we can turn "Help and Feedback" to just "Support" to differentiate the two links.

> 
> The current directive to call us should be removed.

Yes. Remove links to calling support.
> 
> Proposed text (CCing Larissa for comments):
> 
> Give us feedback: http://input.mozilla.org/feedback
> 
> or (preferred) to have just a button that says [GIVE MOZILLA FEEDBACK] or
> something like that which takes you to the above link.

I prefer to make it a button as well. The button text can be "Send Mozilla Feedback" or "Send Us Feedback" if that's too long.
Flags: needinfo?(cwwmozilla)
(Reporter)

Comment 2

5 years ago
I'm not sure, that depends on what UX will think works better.

I think we want to keep the Online support link to telefonica. This is just about removing the call support option and adding a [send feedback] button.

Let's move the discussion of moving the feedback button to a new bug and see what UX wants around that.
Flags: needinfo?(cwwmozilla)

Comment 3

5 years ago
Hi Larissa,

We do need to keep the Online Support: placeholder and the Call Support: placeholder.

I will have the correct Telefonica link and phone number asap, so please don't remove these, we have agreed to it with TEF Support and Ops already. 

Thanks,
Michelle
(Reporter)

Comment 4

4 years ago
Ok, just to reclarify.  This bug is about adding feedback links:

1) Preferred:

A button (like the user guide button) that says. [SEND MOZILLA FEEDBACK]. The button goes to http://input.mozilla.org/feedback

2) Slightly less preferred:

A link (like the Online support link):

Send Mozilla feedback: input.mozilla.org/feedback

Comment 5

4 years ago
Here is an update from TEF on the link target and support number for vivo:

the contact info for Vivo is

 

*8486 or 1058

 

And the url

 

http://www.vivo.com.br/portalweb/appmanager/env/web?_nfls=false&_nfpb=true&_pageLabel=vcAtendMovelBook&WT.ac=portal.atendimento.movel

 

As we comment last week this url will change to something more friendly like www.vivo.com.br/firefoxos and will point to the firefox microsite

Updated

4 years ago
blocking-basecamp: --- → ?

Updated

4 years ago
blocking-basecamp: ? → +
Priority: -- → P2

Updated

4 years ago
Component: General → Gaia::Settings
(Assignee)

Comment 6

4 years ago
Larissa, do you have a wireframe of how this page should look to include all these pieces? Right now there's also a "User guide" button that doesn't do anything for me.

And this change will require string changes, which aren't supposed to be happening anymore :/

Comment 7

4 years ago
Hi Margaret!

Sorry about this, I appreciate your help. I'm in SF today if you want to meet or I'm happy to chat over vidyo/skype. 

Ok, so to pull this all together into one coherent request, this is what we need on the Settings > Help & Feedback screen :

Online support: Vivo (links to 
http://www.vivo.com.br/portalweb/appmanager/env/web?_nfls=false&_nfpb=true&_pageLabel=vcAtendMovelBook&WT.ac=portal.atendimento.movel)

Call support: *8486 or 1058 

No change to User Guide button or link target, the User Guide button is correctly implemented and perfect.

Add a new button below with the text "Send Mozilla Feedback" (links to http://input.mozilla.org/feedback)

The new button request is obviously outside of string freeze, which was an oversight on our part, so we are hoping to 'ride it along' with these changes if at all possible.

Comment 8

4 years ago
Hi again,

The User Guide button was working in a prior build, here is the related bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=799786

It is just like the in-prod links we have in Firefox for Android, where it is a redirected thing, it really was working last week.
(Assignee)

Comment 9

4 years ago
Thanks for the quick response! I'm WFH today, but the outline above is great. I'll try to make a patch for this now so that we can land strings ASAP.

It seems that the issue with the User Guide button for me is that I don't have a 'deviceinfo.os' setting set. This may just be something that gets set while creating released builds, so I won't worry about it (if you notice the button does fail to work, please file a separate bug and I can help investigate).
Assignee: nobody → margaret.leibovic

Comment 10

4 years ago
Margaret, here's what the page should look like: http://people.mozilla.com/~lco/Settings_B2G/Release_1_Specs/R1_Device_v3.pdf

See page 20 onwards.

The link for "Send Mozilla Feedback" should be the first entry in the "Improve Firefox OS" settings page instead.
(Assignee)

Comment 11

4 years ago
(In reply to Michelle Luna from comment #7)

> Call support: *8486 or 1058 

Michelle and I were discussing this on IRC - having two separate numbers messes up the UX for tapping on the entire section opening the link. Also, having a UI that supports one or more numbers is more complicated to implement than just having one number, so having one number would make things easier. Alternately, it would also be easy to implement two phone number rows with different labels. I feel like we should follow up with TEF to find out what the difference is between the two numbers to see if either of these are possibilities.

(In reply to Larissa Co from comment #10)
> Margaret, here's what the page should look like:
> http://people.mozilla.com/~lco/Settings_B2G/Release_1_Specs/R1_Device_v3.pdf
> 
> See page 20 onwards.
> 
> The link for "Send Mozilla Feedback" should be the first entry in the
> "Improve Firefox OS" settings page instead.

According to this mock-up, this section should be labeled "Help" instead of "Help & Feedback". Should I fix that as well?
(Assignee)

Comment 12

4 years ago
(In reply to Larissa Co from comment #10)

> The link for "Send Mozilla Feedback" should be the first entry in the
> "Improve Firefox OS" settings page instead.

Should this be a link or a button?

Comment 13

4 years ago
I would recommend it be a button, but Larissa can confirm.
(Assignee)

Comment 14

4 years ago
I have a WIP here: https://github.com/leibovic/gaia/commit/f8c536538d96a6af37ffbe2d1a1c2069955faf6f

This patch:
* Adds "Send Mozilla Feedback" button to the top of "Improve Firefox OS" http://cl.ly/image/1F2G2p0o1P2Y
* Renames "Help & Feedback" section to "Help"
* Updates links in "Help" section

For now, I just used the first phone number as the "Call support:" number. I can work on making two separate number links, but they'll end up being pretty small hit targets.
(Assignee)

Comment 15

4 years ago
(In reply to Margaret Leibovic [:margaret] from comment #11)
> (In reply to Michelle Luna from comment #7)
> 
> > Call support: *8486 or 1058 
> 
> Michelle and I were discussing this on IRC - having two separate numbers
> messes up the UX for tapping on the entire section opening the link. Also,
> having a UI that supports one or more numbers is more complicated to
> implement than just having one number, so having one number would make
> things easier. Alternately, it would also be easy to implement two phone
> number rows with different labels. I feel like we should follow up with TEF
> to find out what the difference is between the two numbers to see if either
> of these are possibilities.

It turned out it wasn't too hard to implement the two separate phone numbers. The only thing we're sacrificing is the larger tap target. Additionally, I tested that localizes can leave the strings for the "or <second phone number>" part blank, and that will make it so that only one phone number shows up nicely.
(Assignee)

Comment 16

4 years ago
Created attachment 684229 [details]
Link to https://github.com/mozilla-b2g/gaia/pull/6564

The one thing about this patch I'm not too fond of is the one-off styling of the support links, but I couldn't figure out how to do it with magical markup structure :)

Here's a desktop B2G screenshot for those interested: http://cl.ly/image/1p371x2B1S2z
Attachment #684229 - Flags: review?(kaze)
Keywords: late-l10n
Your patch looks OK but I’m not sure we can have operator-specific strings in the Settings l10n resources. Vivien, should we use an operator-specific setting instead?
Flags: needinfo?(21)
(In reply to Fabien Cazenave [:kaze] from comment #17)
> Your patch looks OK but I’m not sure we can have operator-specific strings
> in the Settings l10n resources. Vivien, should we use an operator-specific
> setting instead?

I would like to add such links to a custom/ folder. Same as the browser bookmarks. Sounds ok for me for now.
Flags: needinfo?(21)
Comment on attachment 684229 [details]
Link to https://github.com/mozilla-b2g/gaia/pull/6564

https://github.com/mozilla-b2g/gaia/commit/b6fabd2aac658c6fd579444532e722c9030d95b1

We’ll move the operator-specific strings to another directory later…
Attachment #684229 - Flags: review?(kaze) → review+
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
(Assignee)

Updated

4 years ago
Depends on: 815257
(Assignee)

Comment 20

4 years ago
(In reply to Fabien Cazenave [:kaze] from comment #19)
> Comment on attachment 684229 [details]
> Link to https://github.com/mozilla-b2g/gaia/pull/6564
> 
> https://github.com/mozilla-b2g/gaia/commit/
> b6fabd2aac658c6fd579444532e722c9030d95b1
> 
> We’ll move the operator-specific strings to another directory later…

Thanks for the review. I filed bug 815257 about this, but I'm not sure exactly what we'd want that directory structure to look like.

Comment 21

4 years ago
> According to this mock-up, this section should be labeled "Help" instead of
> "Help & Feedback". Should I fix that as well?

Yes please. It was called "Help & Feedback" until we moved Feedback to "Improve Firefox OS"

Comment 22

4 years ago
(In reply to Chris Lee [:clee] from comment #13)
> I would recommend it be a button, but Larissa can confirm.

Yes, a button would be great. Text remains "Send Mozilla Feedback"
(Assignee)

Comment 23

4 years ago
(In reply to Larissa Co from comment #21)
> > According to this mock-up, this section should be labeled "Help" instead of
> > "Help & Feedback". Should I fix that as well?
> 
> Yes please. It was called "Help & Feedback" until we moved Feedback to
> "Improve Firefox OS"

Great, this fix was part of my patch.

(In reply to Larissa Co from comment #22)
> (In reply to Chris Lee [:clee] from comment #13)
> > I would recommend it be a button, but Larissa can confirm.
> 
> Yes, a button would be great. Text remains "Send Mozilla Feedback"

This, too :)
As a pt-BR localizer, should I assume those are the final values or the online support link is still temporary?


online-support.href=http://www.vivo.com.br/portalweb/appmanager/env/web?_nfls=false&_nfpb=true&_pageLabel=vcAtendMovelBook&WT.ac=portal.atendimento.movel

call-support-link-1.href=tel:*8486

call-support-link-2.href=tel:1058
(Assignee)

Comment 25

4 years ago
Michelle, how should localizers handle these urls/phone numbers? Will the operators update those themselves?
Flags: needinfo?(mluna)
(Assignee)

Updated

4 years ago
Flags: needinfo?(mluna)

Comment 26

4 years ago
verified on unagi build id:  20130103070201
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.