X11 user agent string on Wayland
Reported by
philip.g...@gmail.com,
Nov 15 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.100 Safari/537.36 Steps to reproduce the problem: 1. Start Chrome in a Wayland session (so X11 isn't used) 2. Look at the user agent string 3. Notice X11 in the string What is the expected behavior? What went wrong? Since X11 isn't used, it would be more logical to use 'Wayland' instead of 'X11' in the user agent string. Did this work before? N/A Chrome version: 54.0.2840.100 Channel: stable OS Version: Arch Linux Gnome 3.22 Flash Version: Shockwave Flash 23.0 r0 See my user agent string above for an example
,
Nov 16 2016
,
Nov 25 2016
Adding TE-NeedsTriageHelp label for further investigation. Thanks...!!
,
Oct 27 2017
,
Nov 2 2017
Closing this issue given the lack of feedback from the reporter. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by thomasanderson@chromium.org
, Nov 16 2016