Allow user to select the material design look as an option
Reported by
synth...@gmail.com,
May 28 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36 Steps to reproduce the problem: Nothing to reproduce as this is a feature. What is the expected behavior? The the user to choose whether or not they want to use the "material design" theme seen in 51.0.2704.63. This could be an option in "Settings" or something in chrome://flags. What went wrong? 51.0.2704.63 introduces a "material design" look that is not favorable by all users. Furthermore, the look is not configurable, which means the aforementioned users now have two options: to use an old version (which introduces inherent security problems) or a version that forces the design changes on the user. It would be much better to include the previous design look in the Chromium engine and allow users to pick which flavor they would like to use. This could be an option in "Settings" or something in chrome://flags. Did this work before? N/A Chrome version: 51.0.2704.63 Channel: stable OS Version: Arch Linux Flash Version: Shockwave Flash 21.0 r0 I have attached two images: * chromium_blue.png: The look of 50.0.2661.94. * chromium_material.png: The look of 51.0.2704.63.
,
May 29 2016
There is chrome://flags/#top-chrome-md But "Non-material" choice does nothing on Chromium 51.0.2704.63, Chrome 51.0.2704.63. However, it still works on Chrome 52.0.2743.10 dev.
,
May 30 2016
The real bug here is that the setting mentioned in Comment 2 doesn't function correctly.
,
May 30 2016
@3: https://bugs.chromium.org/p/chromium/issues/detail?id=595108 The flag is broken (& fixed), in M51 command line way still works: --top-chrome-md=non-material
,
May 30 2016
@4: good catch on the CLI option. Seems like this issue should be merged into that one.
,
Jun 23 2016
Seems like the option in about://flags and the CLI option are both ignored in 51.0.2704.103.
,
Jun 23 2016
Scratch that: it seemed to only happen after launching the first time when upgrading from 51.0.2704.84 to 51.0.2704.103. After closing Chromium (and ensuring that background processes have been terminated), Chromium then launches with the non-material look. Perhaps it had to do something with migrating settings? Not sure.
,
Jun 26 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 Deleted