[opensuse] chromium unconditionally enables threaded-compositing, overriding user's choice
5 Mar
2014
5 Mar
'14
19:44
Hello, See https://code.google.com/p/chromium/issues/detail?id=328177 for details. In summary, the option --enable-threaded-compositing is appended to the command line when launching chromium, which renders the user's choice in chrome://flags irrelevant. Although this option has been in the launcher script for a long time without any side-effect, recently I found out that it causes tab content rendered by plugins to disappear. Why is this option enabled by default, since it is an experimental feature and there is no way to disable it if it causes problems, unless one edits the launch script? Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
3940
Age (days ago)
3940
Last active (days ago)
0 comments
1 participants
participants (1)
-
auxsvr@gmail.com