976571 - Translation infobar option to report language detection problem

Status: RESOLVED WONTFIX

(Firefox :: Translations, defect)

Description

[:Felipe Gomes (needinfo for replies!)]

When Firefox detects the language of a webpage, in the "Options" dropdown in the infobar we want to have an option that says:

- Not in {Detected Language}? Report this to Firefox

Comment 1

[Florian Quèze [:florian]]

Mass move of translation bugs to the new Translation component.

Comment 2

[:Gijs (he/him)]

(In reply to :Felipe Gomes from comment #0)
> When Firefox detects the language of a webpage, in the "Options" dropdown in
> the infobar we want to have an option that says:
> 
> - Not in {Detected Language}? Report this to Firefox

Why is this in the (prioritized!) backlog with a points estimate (!?) when there is no API, no service to talk to, and no design for what the resulting UI is like (how do we display progress / success for reporting the issue, plus a thank you to the user for helping us improve translation?)

Comment 3

[Marco Mucci [:MarcoM]]

(In reply to :Gijs Kruitbosch from comment #2)
> (In reply to :Felipe Gomes from comment #0)
> > When Firefox detects the language of a webpage, in the "Options" dropdown in
> > the infobar we want to have an option that says:
> > 
> > - Not in {Detected Language}? Report this to Firefox
> 
> Why is this in the (prioritized!) backlog with a points estimate (!?) when
> there is no API, no service to talk to, and no design for what the resulting
> UI is like (how do we display progress / success for reporting the issue,
> plus a thank you to the user for helping us improve translation?)

Hi Gijs, this bug is simply in the backlog and hasn't been prioritized by GMC yet for an upcoming iteration to be worked on.

Comment 4

[:Felipe Gomes (needinfo for replies!)]

Yeah, there's no plan in the short term to work on this, it was just added to the backlog for the future. If it appeared in the priority backlog (I see it's there, way down on the list), it was just a mistake.
The bug dependencies are marked correctly and this bug can't be worked on before we have a service spec for it.

Comment 5

[:Gijs (he/him)]

(In reply to Marco Mucci [:MarcoM] from comment #3)
> (In reply to :Gijs Kruitbosch from comment #2)
> > (In reply to :Felipe Gomes from comment #0)
> > > When Firefox detects the language of a webpage, in the "Options" dropdown in
> > > the infobar we want to have an option that says:
> > > 
> > > - Not in {Detected Language}? Report this to Firefox
> > 
> > Why is this in the (prioritized!) backlog with a points estimate (!?) when
> > there is no API, no service to talk to, and no design for what the resulting
> > UI is like (how do we display progress / success for reporting the issue,
> > plus a thank you to the user for helping us improve translation?)
> 
> Hi Gijs, this bug is simply in the backlog and hasn't been prioritized by
> GMC yet for an upcoming iteration to be worked on.

I'm confused. This was not true when I asked (it was in the 32.2 backlog) and it is still not true now, because it's also in the 32.3 backlog (row 94). If it hasn't been prioritized, why is it in there? Should it just be removed?

Comment 6

[Marco Mucci [:MarcoM]]

(In reply to :Gijs Kruitbosch from comment #5)
> (In reply to Marco Mucci [:MarcoM] from comment #3)
> > (In reply to :Gijs Kruitbosch from comment #2)
> > > (In reply to :Felipe Gomes from comment #0)
> > > > When Firefox detects the language of a webpage, in the "Options" dropdown in
> > > > the infobar we want to have an option that says:
> > > > 
> > > > - Not in {Detected Language}? Report this to Firefox
> > > 
> > > Why is this in the (prioritized!) backlog with a points estimate (!?) when
> > > there is no API, no service to talk to, and no design for what the resulting
> > > UI is like (how do we display progress / success for reporting the issue,
> > > plus a thank you to the user for helping us improve translation?)
> > 
> > Hi Gijs, this bug is simply in the backlog and hasn't been prioritized by
> > GMC yet for an upcoming iteration to be worked on.
> 
> I'm confused. This was not true when I asked (it was in the 32.2 backlog)
> and it is still not true now, because it's also in the 32.3 backlog (row
> 94). If it hasn't been prioritized, why is it in there? Should it just be
> removed?

Yes, you are correct and it is a mistake that it is present in the prioritized list.  I missed Felipe's note in Comment #4 that it should have been removed.  Thanks for bringing it up.  I'll remove it now.

Comment 7

[:Felipe Gomes (needinfo for replies!)]

We'll have FHR data on how often users switch the detected language (bug 977770), and we have bugzilla, input.mozilla.org and other venues for users to report detection problems for us, so with that this service doesn't look necessary at the moment.