Issue 228830 in chromium: The command line switch --disable-new-menu-style only works when chrome is not running in the background.

99 views
Skip to first unread message

chro...@googlecode.com

unread,
Apr 8, 2013, 10:02:25 AM4/8/13
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: Cr-UI Pri-2 Via-Wizard Type-Bug OS-Windows

New issue 228830 by Eric.Dic...@gmail.com: The command line switch
--disable-new-menu-style only works when chrome is not running in the
background.
http://code.google.com/p/chromium/issues/detail?id=228830

UserAgent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.31 (KHTML, like
Gecko) Chrome/26.0.1410.43 Safari/537.31

Steps to reproduce the problem:
1. Leave the "Continue running background apps when Google Chrome is
closed" setting checked
2. Edit a chrome shortcut to include --disable-new-menu-style
3. Try to launch chrome (the command line switch doesn't change anything)

OR

1. Leave the "Continue running background apps when Google Chrome is
closed" setting checked
2. Edit a chrome shortcut to include --disable-new-menu-style
3. Close chrome form the system tray
4. Launch chrome (works like intended at this point)
5. Reboot the computer
6. Launch chrome again (not working anymore)

What is the expected behavior?
--disable-new-menu-style should work by just adding to the shortcut, you
shouldn't have to close or disable the background processes to get it
working.

What went wrong?
The new menu style still appears even when using a shortcut with
--disable-new-menu-style

Did this work before? Yes Before the update you didn't even have to use a
switch to get good looking menus

Chrome version: 26.0.1410.43 Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)

This should really be a setting within chrome and not a command line switch
anyway. A command line switch would be fine for the Dev channel or maybe
even the Beta channel but this is the Stable channel, we should not have to
hack to make it a usable browser.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

chro...@googlecode.com

unread,
Apr 9, 2013, 12:43:16 PM4/9/13
to chromi...@chromium.org

Comment #1 on issue 228830 by robertco...@yahoo.com: The command line
switch --disable-new-menu-style only works when chrome is not running in
the background.
http://code.google.com/p/chromium/issues/detail?id=228830

What is with Chrome having options that have to be set via a command-line
flag? That is extremely limited given that Chrome is launched from a
multiple of ways such as from clicking on a .URL file, clicking on a .HTM
file, directly entering an HTTP address into the Run box, etc. So to change
an option - we have to change that flag in multiple locations in .LNK files
in our Start Menu and also search our registry and edit it at multiple
locations such as HKEY_CLASSES_ROOT\http\shell\open\command ?

All options should be able to be set via about:flags or read from some INI
file so that they can be set from one location no matter how the Chrome EXE
is launched.

chro...@googlecode.com

unread,
Apr 22, 2013, 12:09:31 PM4/22/13
to chromi...@chromium.org
Updates:
Status: WontFix

Comment #2 on issue 228830 by stro...@chromium.org: The command line switch
--disable-new-menu-style only works when chrome is not running in the
background.
http://code.google.com/p/chromium/issues/detail?id=228830

Command line switches are working as intended. The new menu style is an
intentional change, and the old style is unsupported. You should not depend
on it working correctly or being present in the future.

chro...@googlecode.com

unread,
Apr 22, 2013, 12:17:32 PM4/22/13
to chromi...@chromium.org

Comment #3 on issue 228830 by Toa.Im...@gmail.com: The command line switch
--disable-new-menu-style only works when chrome is not running in the
background.
http://code.google.com/p/chromium/issues/detail?id=228830

BUT PEOPLE HATE NEW MENU STYLE!!!

chro...@googlecode.com

unread,
Apr 30, 2013, 7:16:58 AM4/30/13
to chromi...@chromium.org

Comment #4 on issue 228830 by ty...@mango.net.nz: The command line switch
--disable-new-menu-style only works when chrome is not running in the
background.
http://code.google.com/p/chromium/issues/detail?id=228830

This is dumb. I actually filed a bug as I thought it was broken. This
should be a about:flag setting or something. I don't want big menus on my
tiny screen. Next Chrome will be telling me the Windows8 Start menu is
great on my non-touch device.

I love chrome, but I HATE the new chubby menus.

chro...@googlecode.com

unread,
Apr 30, 2013, 7:24:30 AM4/30/13
to chromi...@chromium.org

Comment #5 on issue 228830 by ty...@mango.net.nz: The command line switch

chro...@googlecode.com

unread,
Apr 30, 2013, 7:25:30 AM4/30/13
to chromi...@chromium.org

Comment #6 on issue 228830 by ty...@mango.net.nz: The command line switch
--disable-new-menu-style only works when chrome is not running in the
background.
http://code.google.com/p/chromium/issues/detail?id=228830

Sorry for the double posts. Posting here on chrome gave me this error. Had
to go back to firefox to post here

400. That’s an error.

Your client has issued a malformed or illegal request. That’s all we know.
Reply all
Reply to author
Forward
0 new messages