New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 906082 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Task



Sign in to add a comment

Add UMA for use of fallback language

Project Member Reported by tiborg@chromium.org, Nov 16

Issue description

If Chrome is an app bundle with language splits it can happen that it starts in a language other than the system language (see b/119244673 for more context). We should track via UMA how often this happens. More specifically, implement metrics 3 and 3 in [1]:

# Metric 2

The number of times Chrome starts/resumes in a language other than the system language but we support the system language. This requires language splits to be turned on. It will tell us whether regular language splits are sufficient and is therefore also a predictor whether we can launch in Stable. We currently have language splits turned on in Canary and Dev. To get more metrics we could also turn them on in Beta.

Histogram name: Android.Language.WrongLanguageAfterResume
Histogram type: Boolean

# Metric 3

The duration from Chrome starting in a language other than the system language and we support the system language until it starts in that system language. This can reveal whether certain groups have an oddly high latency and/or a potential bug. This also requires language splits to be turned on.

Histogram name: Android.Language.DurationUntilCorrectLanguageApplied
Histogram type: Time

[1] https://docs.google.com/document/d/1_bOFM-xOYkzW_XccIijh-zNutzsNRcGGYylVl9ivBhI
 
#3 is good because it shows that it's in maybe the secondary or tertiary language set on the device (but still not falling back to EN).
Discussed with Ben offline, maybe we want to split 2. into two:

2a. as 2. but Chrome supports system language
2b. as 2. but Chrome doesn't support system language

2b would actually be what we want while 2a is something we would want to avoid.
Labels: -Target-72 Target-73

Comment 4 by tiborg@chromium.org, Jan 18 (4 days ago)

We agreed on the metrics defined in [1]. For the fallback language this means Metric 2 and 3. Will update bug accordingly.

[1] https://docs.google.com/document/d/1_bOFM-xOYkzW_XccIijh-zNutzsNRcGGYylVl9ivBhI

Comment 5 by tiborg@chromium.org, Jan 18 (4 days ago)

Components: UI>Internationalization

Comment 6 by tiborg@chromium.org, Jan 18 (4 days ago)

Description: Show this description

Sign in to add a comment