Issue metadata
Sign in to add a comment
|
Site permissions still unreachable after 1+ year of their removal
Reported by
vphan...@gmail.com,
Mar 3 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36 Steps to reproduce the problem: 1. Click the icon to the left of the address bar 2. Notice in "Permissions" the single "Site settings" hyperlink and absence of actual permissions (i.e. disabling JavaScript) 3. Clicking "Site settings" goes to the GLOBAL chrome://settings/content 4. Something as trivial as disabling JavaScript for the current site now requires to fish for JavaScript in chrome://settings/content, click "Manage exceptions", then see if there's already an entry for the current domain and, if not, create one by manually typing the host/domain and saving. What is the expected behavior? If you're still convinced that hiding permissions behind a "Site settings" link in the now wrongly-named "Permissions" tab of this pop-up, at least do as promised (I can't find the issue number...) and link to a panel which is SPECIFIC to the current site, as before, to avoid users fishing for settings and manually transcribing the site's host name multiple times (a risky source of errors). What went wrong? This is a security concern because average users will not likely go through the trouble necessary to add any individual site permission restrictions, whereas all permissions USED to be offered very clearly in that site pop-up. Did this work before? Yes January, 2015 roughly Chrome version 40 Chrome version: 48.0.2564.116 Channel: stable OS Version: 4.2.0 Flash Version: Shockwave Flash 20.0 r0
,
Mar 3 2016
Thanks for reporting this issue, vphantom! +palmer@, would you mind chiming in?
,
Mar 3 2016
Yep, we're going to revert the change, since the replacement UI never materialized. Hopefully for M50.
,
Dec 9 2016
Security>UX component is deprecated in favor of the Team-Security-UX label |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by vphan...@gmail.com
, Mar 3 2016