Could someone please confirm this issue? as we are seeing the above behavior irrespective of "#top-chrome-md" flag status in chrome://flags.
Chrome#51.0.2692.0
OS: Linux Ubuntu 14.04
Thank you!
the infobars are fine, but about:flags isn't working because Chrome sets the mode based on the command line before it loads the profile and the associated about:flags entries. Rearranging startup tasks to fix seems fraught with peril (and just un-initing the mode when about:flags initialization finally happens might leave us in a weird state where some things thought they were in MD and some didn't). Bottom line --- the command line flag still works.
Stack trace 1:
#0 0x7f31a1f5a39e base::debug::StackTrace::StackTrace()
#1 0x7f31a23ccfa2 ui::MaterialDesignController::InitializeMode()
#2 0x7f31a23cd1c7 ui::MaterialDesignController::IsModeMaterial()
#3 0x7f31a23d17c1 ui::ResourceBundle::LoadChromeResources()
#4 0x7f31a23cff08 ui::ResourceBundle::InitSharedInstanceWithLocale()
#5 0x7f31a1b4ebcc ChromeMainDelegate::PreSandboxStartup()
#6 0x7f31a1f2b960 content::ContentMainRunnerImpl::Initialize()
#7 0x7f31a1f2a9ca content::ContentMain()
#8 0x7f31a1b4e298 ChromeMain
#9 0x7f319aaa4ec5 __libc_start_main
#10 0x7f31a1b4e169 <unknown>
Stack trace 2:
#0 0x7f5c9aec739e base::debug::StackTrace::StackTrace()
#1 0x7f5c9b339fa2 ui::MaterialDesignController::InitializeMode()
#2 0x7f5c9b33a1c7 ui::MaterialDesignController::IsModeMaterial()
#3 0x7f5c9d926c11 libgtk2ui::Gtk2UI::LoadGtkValues()
#4 0x7f5c9d92682b libgtk2ui::Gtk2UI::Initialize()
#5 0x7f5c9ace988a ChromeBrowserMainParts::ToolkitInitialized()
#6 0x7f5c9d35587e content::BrowserMainLoop::InitializeToolkit()
#7 0x7f5c9d180fc6 content::BrowserMainRunnerImpl::Initialize()
#8 0x7f5c9d180b76 content::BrowserMain()
#9 0x7f5c9ae98c7a content::ContentMainRunnerImpl::Run()
#10 0x7f5c9ae979e0 content::ContentMain()
#11 0x7f5c9aabb298 ChromeMain
#12 0x7f5c93a11ec5 __libc_start_main
#13 0x7f5c9aabb169 <unknown>
The top-chrome-md=non-material is not working in Linux, when set either from the command line or in about:flags. This became apparent when MD became the default for linux in m51 ( issue 591715 ).
This has been reported by several linux users in the help forum
https://productforums.google.com/forum/#!topic/chrome/WUAvRiyd1Bk
When did it land? I'm seeing recent reports of top-chrome-md=non-material not working that I assume are for Linux 51.0.2704.36 or .47?
How do I track this commit: refs/heads/master@{#387186} to the distributed release refs/branch-heads/2704@{#xxx} value?
Thanks
Chromium M-51 was branched at r386251 which is before the commit that has fixed this bug (r387186). M-51 still has the bug since that commit was never merged. We don't currently plan to merge this into M-51. In M-51 MD can still be disabled using command line (but not on chrome://flags page).
Comment 1 by ajuma@chromium.org
, Mar 15 2016