Disabling a flag in chrome://flags doesn't work

1,825 views
Skip to first unread message

Alex Hutter

unread,
Apr 10, 2013, 4:36:42 PM4/10/13
to chromi...@chromium.org
I'm on a local chromeos build.  I disabled a flag in chrome://flags and restarted. chrome://flags shows the flag as being disabled but it's still present in the Command Line section of chrome://chrome in the --flag-switches section.  Anyone know how to fix this?

Thanks!

Nico Weber

unread,
Apr 10, 2013, 4:41:44 PM4/10/13
to ahu...@google.com, Chromium-dev, pasta...@chromium.org
Does "local chromeos build" mean a full chromeos build or a linux build with chromeos=1 in GYP_DEFINES? Is your local build managed?

Nico


On Wed, Apr 10, 2013 at 1:36 PM, Alex Hutter <ahu...@google.com> wrote:
I'm on a local chromeos build.  I disabled a flag in chrome://flags and restarted. chrome://flags shows the flag as being disabled but it's still present in the Command Line section of chrome://chrome in the --flag-switches section.  Anyone know how to fix this?

Thanks!

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
 
 
 

Alex Hutter

unread,
Apr 10, 2013, 4:43:04 PM4/10/13
to chromi...@chromium.org, ahu...@google.com, pasta...@chromium.org
Linux build with chromos=1 in GYP_DEFINES.  Not sure what you mean by "managed".

Thiago Farina

unread,
Apr 10, 2013, 9:14:39 PM4/10/13
to ahu...@google.com, Chromium-dev, pasta...@chromium.org, Nico Weber
On Wed, Apr 10, 2013 at 5:43 PM, Alex Hutter <ahu...@google.com> wrote:
> Linux build with chromos=1 in GYP_DEFINES. Not sure what you mean by
> "managed".
>
I think by that, Nico means the "managed" entry we have in ../.gclient
file. If the entry is set to True than it's managed :)

--
Thiago

Alex Hutter

unread,
Apr 10, 2013, 9:24:16 PM4/10/13
to chromi...@chromium.org, ahu...@google.com, pasta...@chromium.org, Nico Weber
Yep. "managed" is set to True.

Julian Pastarmov

unread,
Apr 11, 2013, 4:15:50 AM4/11/13
to chromi...@chromium.org
I think the problem you see is that on a linux chromeos build you are not really using the owner account and thus you are only touching the flags in your profile instead of the global flags stored in Local State. I am currently working on allowing user control for flags that will be active in their respective session only and this is why you see the UI enabled at all. However since the work is not yet finished you can change them but they are not applied yet. I hope this to be fixed soon but even then I don't think this will work as you expect in linux builds since it will require restart of the browser which will not work without the session manager. 

If you need to specify/change flags on the linux build - go to your profile dir open the Local Settings file and find the "browser" section and inside it the "enabled_labs_experiments" value and add or remove whichever flags you wish to have.

-Julian
Reply all
Reply to author
Forward
0 new messages