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

Issue 694127 link

Starred by 1 user
Status: Fixed
Owner:
jinsuk...@chromium.org
Closed: Feb 2017
Cc:
nyerramilli@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Wrong translation is seen for Hindi language on Welcome page.

Reported by dchau...@etouch.net, Feb 20 2017 
Chrome Version: 58.0.3018.0 (Official Build)5e7216844858ad1d08a70ac7aeef88547db2be7f-refs/heads/master@{#451537} 32/64-bit.
OS: Windows(7,8,8.1,10).

What steps will reproduce the problem?
1. Launch chrome and go to chrome://welcome page.
2. Change the browser language to Hindi from chrome://settings/languages
3. Now, go back to chrome://welcome page and observe.

Wrong translation is seen for Hindi language.
Welcome page should seen on Hindi language.

This is a regression issue, broken in M-58 series, below is manual regression range.

Good build: 58.0.3015.0
Bad build: 58.0.3016.0

Note: This issue is not seen on Mac and Linux OS.

Kindly review the attached screen-cast for reference.
Actual behavior.mp4
1.3 MB View Download
Expected behavior.mp4
1.1 MB View Download

Comment 1 by nyerramilli@chromium.org, Feb 20 2017

Labels: hasbisect-per-revision ReleaseBlock-Stable
Owner: jinsuk...@chromium.org
Status: Assigned (was: Unconfirmed)
adding blocker label as this is recent regression, please change if required..

Using the per-revision bisect providing the bisect results,
Good build: 58.0.3015.0 (Revision: 451180)
Bad build: 58.0.3016.0 (Revision: 451403)

You are probably looking for a change made after 451193 (known good), but no later than 451194 (first known bad).
CHANGELOG URL:
The script might not always return single CL as suspectas some perf builds might get missing due to failure.
  https://chromium.googlesource.com/chromium/src/+log/625c0cc94b7ee0441ac0debc5f295727f526eafd..89967f02f2402870acb8322ad50c391b3a0971e7

jinsukkim@, could you please check the issue and help.

Comment 2 by jinsuk...@chromium.org, Feb 21 2017

Status: Started (was: Assigned)
Project Member

Comment 3 by bugdroid1@chromium.org, Feb 21 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/e2221203908694ce026c037e9d084485a1f92c81

commit e2221203908694ce026c037e9d084485a1f92c81
Author: jinsukkim <jinsukkim@chromium.org>
Date: Tue Feb 21 21:56:28 2017

Add missing charset tag to html resources

I18N-resource html files should have an explicit charset tag
specificying their encoding in accordance with the recent changes that
do not auto-detect UTF-8 encoding. See https://crrev.com/2697213002

BUG= 694127 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

Review-Url: https://codereview.chromium.org/2706883002
Cr-Commit-Position: refs/heads/master@{#451843}

[modify] https://crrev.com/e2221203908694ce026c037e9d084485a1f92c81/chrome/browser/resources/welcome/welcome.html
[modify] https://crrev.com/e2221203908694ce026c037e9d084485a1f92c81/chrome/browser/resources/welcome/win10/inline.html
[modify] https://crrev.com/e2221203908694ce026c037e9d084485a1f92c81/chrome/browser/resources/welcome/win10/sectioned.html

Comment 4 by jinsuk...@chromium.org, Feb 21 2017

Status: Fixed (was: Started)
►

Sign in to add a comment