Visual feedback when change site settings from
Reported by
smo...@gmail.com,
Jun 7 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/58.0.3029.110 Chrome/58.0.3029.110 Safari/537.36 Steps to reproduce the problem: 1. Click on the leftmost button of the omnibar (has a name?) 2. Change a default settings (e.g. Disable JavaScript) 3. Refresh the page. What is the expected behavior? I would see a visual feedback which informs me that the default settings has changed. What went wrong? There is no feedback. Did this work before? N/A Chrome version: 58.0.3029.110 Channel: stable OS Version: 4.8.0-53-generic Flash Version: Shockwave Flash 25.0 r0 Since the settings stay the same after browser restart you may have forgotten that some feauter is disabled here or there, thus you may need some time to realize that everything is working properly but you've just disabled something.
,
Jun 7 2017
,
Jun 8 2017
+cc lgarron. More generally, we are thinking of how to better communicate what is and isn't currently allowed on a page. It's tricky though - we have a delicate balance between what is understandable, what is useful, and what can fit into the UI.
,
Jun 8 2017
I think there is no need to show any single feature which has been disabled but it would enough to highlight an (new ad-hoc) icon or show a little symbol near the omnibar. In any case, I enjoy the fact that you agree on putting a visual feedback for it.
,
Nov 10 2017
,
Feb 18 2018
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by jdonnelly@chromium.org
, Jun 7 2017