New issue
Advanced search Search tips

Issue 714472 link

Starred by 1 user
Status: Fixed
Owner:
lafo...@chromium.org
Closed: Apr 2017
Cc:
napper@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

[Component Request] UI>Browser>Language

Project Member Reported by yyushkina@chromium.org, Apr 23 2017 
1] Component Name: UI>Browser>Language

2] Parent Component: UI>Browser
3] Description of Component: A component for bugs related to incorrect or unexpected language of pages being served. Distinct from UI>Browser>Translate which is reserved for Translate bugs.

4] Admin/ Owner: napper@, yyushkina@

5] Please specify what triage practices will be followed for the component
(i.e. what team will do it and how frequently). The Chrome Language will triage the component on a regular basis.

Comment 1 by lafo...@chromium.org, Apr 25 2017 

The component name seems like it will confuse people, is there an alternate phrasing that better distinguishes from Translate and things like spell check?

Comment 2 by yyushkina@chromium.org, Apr 25 2017 

Translate and Spellcheck are ultimately subsets of Language bugs but they don't cover all of them hence the desire to create this component. 

Here' s another idea: Could we move Translate and Spellcheck under UI>Browser>Language component after it's created or is that too disruptive?

Comment 3 by lafo...@chromium.org, Apr 27 2017

Owner: lafo...@chromium.org
Status: Fixed (was: Untriaged)
Thank you, that's a great idea.  Indeed a bit more work (had to manually move 2500 issues w/ bulk edit), but that's an excellent suggestion that keeps the tree logical.

I've created the Language component and 2 new components Spellcheck and Translate underneath.

Comment 4 by yyushkina@chromium.org, Apr 27 2017 

Thank you!!!
►

Sign in to add a comment