Issue metadata
Sign in to add a comment
|
VPN UI no longer clearly distinguishes Android from Chrome OS VPN
Reported by
ad...@mattprager.com,
Jan 9 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10176.41.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.79 Safari/537.36 Platform: 10176.41.0 (Official Build) beta-channel cyan Steps to reproduce the problem: 1. Click Chrome OS notifications. 2. VPN indicates Connected to a VPN - only it's actually an Android VPN. 3. What is the expected behavior? Chrome OS notification bar should only show Chrome OS information or clearly indicate it's showing Android information as well. What went wrong? Chrome OS has two notifications bars, one for Android notifications and one for Chrome OS notifications. In previous versions, and Android VPN would only show up in the Android notification as only Android would be going through that VPN and Chrome OS would be accessing the internet normally or going through its own VPN. In the current version, a VPN notification shows up in the Chrome OS section only it's NOT for Chromes OS; it's for Android. This same notification also shows up in the Android notification section. Since Chrome OS is not, in fact, being routed through the Android VPN, it should not appear that way in the UI as it's confusing for the end user. The only way to find out that the VPN is actually being started by Android rather than Chrome OS is by digging deep into the settings menu where it's eventually indicated that the VPN provider is Android. The current UI makes it appear that both Chrome OS and Android are being run through a VPN. As this is incorrect - and pretty insecure actually as an end user might this s/he's protected when in fact s/he isn't - I think it should revert to the old behavior where an Android-only VPN notification only showed up in the Android notification section rather than telling a user they're protected when in reality they aren't, at least not via Chrome OS connections. Did this work before? Yes Previous beta. Chrome version: 64.0.3282.79 Channel: beta OS Version: 10176.41.0 Flash Version: 28.0.0.137
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by omrilio@chromium.org
, Jan 12 2018Owner: keta...@chromium.org