Issue metadata
Sign in to add a comment
|
Element inspector not working when LANG env var is set to non-US
Reported by
kevinsaw...@gmail.com,
Apr 25 2017
|
||||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36
Steps to reproduce the problem:
1. Launch Chrome via `LANG=de_DE.UTF-8 /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome https://google.com`
2. Open the dev tools
3. Select the element highlighter button on the top left
4. Hover over an element in the page
What is the expected behavior?
Hovered element is highlighted with size and element name
What went wrong?
Nothing appears when hovering over any elements
Did this work before? N/A
Chrome version: 58.0.3029.81 Channel: stable
OS Version: OS X 10.12.4
Flash Version: Shockwave Flash 25.0 r0
Console output includes the following error:
[39409:775:0425/154223.903154:ERROR:CONSOLE(3075)] "Protocol Error: the message without method: {"error":{"code":-32700,"message":"Message must be a valid JSON"}}", source: chrome-devtools://devtools/bundled/inspector.js (3075)
Could also reproduce this in 60.0.3080.0 canary.
Works fine when using a LANG value of en_US.UTF-8
,
Apr 26 2017
Able to reproduce the issue on Mac 10.12.4 using chrome reported version #58.0.3029.81 and latest chrome version #60.0.3080.5. Bisect Information: ===================== Good build: 54.0.2828.0 Revision(411828) Bad Build : 54.0.2829.0 Revision(411902) Note: Providing the CL from omahaproxy as running the bisect build won't be able to invoke chrome via `LANG=de_DE.UTF-8 /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome https://google.com` using command prompt. Change Log URL: (From Omahaproxy) https://chromium.googlesource.com/chromium/src/+log/54.0.2828.0..54.0.2829.0?pretty=fuller&n=10000 Unable to find any possible suspect from the above CL. Could anyone from dev team please help us in assigning it to the right owner. Thanks...!!
,
Apr 27 2017
May be this patch is the suspect, not sure though- https://chromium.googlesource.com/chromium/src/+/299805a3efd15f7464d2a768051b9f107adc09a4 Assigning to CL owner for further updates.
,
Apr 27 2017
Alexey, could you please take a look? Sounds like floating point serialization issue.
,
Apr 27 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ligim...@chromium.org
, Apr 25 2017