![]() ![]() ![]() I first thought that the background color of the lines indicate whether it is turned on or not, but that is not the case as it simply reveals if the state of the feature has been changed by the user. The Overlay Scrollbars experiment lists its state as "default", but does not reveal whether that means that it is enabled or not. The screenshot above highlights why this is a problem. The main issue however are experiments that use menus instead of links to change their state, as there is no indication whether a feature is enabled or not if a menu is used. If you see "enable", it is disabled at the time, and if you see "disable", it is enabled. This is a good indicator of whether the experiment is enabled or not. ![]() Most list an "enable" or "disable" link that you can click on to either enable or disable the feature. When you open chrome:// flags in the browser you will notice that Google uses different mechanics to configure the state of these preferences in the browser. Recent examples of the capabilities that the chrome://flags page provides users with include enabling material design pages, or enabling audio-muting way before the feature landed in Chrome. Chrome users can enable these features on the page to test new functionality before it lands in the browser, or is pulled from it again by Google. ![]()
0 Comments
Leave a Reply. |