Issue metadata
Sign in to add a comment
|
Regression:Language translation is not applied on remote NTP after changing browser language.
Reported by
pranjali...@etouch.net,
Oct 30
|
||||||||||||||||||||
Issue descriptionChrome Version: 72.0.3595.2 (Official Build) 4af8b5a14fa87ad1e81fa9ae20c30f9a8c1494cb-refs/branch-heads/3595@{#4}(32/64 bit) OS: Win(7,8,8.1,10) OS Steps to reproduce: 1. Launch chrome, navigate to chrome://flags, click on 'Reset all to default' and relaunch browser. 2. Now change browser language to 'French' and again relaunch browser. 2. Open NTP and observe. Actual : Language translation is not applied on remote NTP after changing browser language. Expected: Language translation should be applied on remote NTP after changing browser language. This is a regression issue, broken in 'M-70', and below is the bisect info: Good Build: 70.0.3537.0 (Revision: 587303) Bad Build : 70.0.3538.0 (Revision: 587811) Change-Log URL: https://chromium.googlesource.com/chromium/src/+log/70.0.3537.0..70.0.3538.0?pretty=fuller&n=10000 Suspecting: r587382 ? @sweilun: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Note: 1.Unable to provide 'per-revision' bisect as it shows "We don't have enough builds to bisect" error message. 2.Tried on other machines but still getting the same error again. 3.Unable to perform 'chromium bisect' script as issue is not reproducible on chromium builds, hence providing suspect through Manual change-log. 4.Above issue is seen only on remote NTP not on local NTP. 5.Issue is not seen on Linux(14.04 LTS) and Mac(10.13.1 , 10.13.6 , 10.14.1).
,
Nov 6
,
Nov 15
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by twelling...@chromium.org
, Oct 30