Issue metadata
Sign in to add a comment
|
The --lang=en_GB flag doesn't appear to work with --headless in Chrome 60 Beta
Reported by
georgegr...@gmail.com,
Jun 13 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.24 Safari/537.36 Steps to reproduce the problem: 1. Launch Chrome Headless with the --lang=en_GB flag and --headless (and the additional headers described in your docs) 2. Observe that locale is not enforced, on things such as date-time strings. What is the expected behavior? I have a Karma Unit Test configuration which launches Google Chrome to run tests, contains some unit tests that test for locale formatted Date-Time strings. When setting the --lang flag to =en_GB I expect that my unit tests that output date-time strings should be in the correct locale format. I would expect the same behaviour could be observed outside of Karma, launching headless chrome with the --lang flags to set the locale of the browser. What went wrong? My unit tests fail and use the default en_US date format. Did this work before? No Chrome version: 60.0.3112.24 Channel: beta OS Version: 10.0 Flash Version: This is the first time Headless has been available for Windows, but without the --headless flag my unit tests succeed.
,
Jun 19 2017
,
Jun 19 2017
georgegriffiths2502@ - Thanks for filing the issue...!! Could you please provide a sample test file to test the issue from TE-end. This will help us in triaging the issue further. Thanks...!!
,
Jul 10 2017
Could you please respond to comment #3.Are you still facing this issue on latest beta 60.0.3112.50? Please try the issue on latest beta new profile without any extensions/flags and update the thread if the issue still persists. Thanks,
,
Jul 25 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by kavvaru@chromium.org
, Jun 15 2017