Display a warning when the user tries to launch with --app-id= while defaulting to --incognito mode
Reported by
arnold.n...@googlemail.com,
May 14 2016
|
|||
Issue description
Chrome Version : 49.0.2623.108
OS Version: Ubuntu 16.04 LTS xenial Linux host 4.4.0-22-generic #39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:
What steps will reproduce the problem?
1. Install chromium-browser on ubuntu xenial amd64 (probably does not really matter which version)
2. Edit /etc/chromium-browser/default to include CHROMIUM_FLAGS="--incognito" to make chromium default to incognito mode.
3. Install an app from chrome.google.com (possible from extensions menu, non incognito mode)
4. In chromium app overview right click on that app and choose "Create Link" then tick both Desktop and Apps-menu.
5. Launch that .desktop file (which chromium closed before)
6. Launch chromium-browser from command line with that Exec=... command from the .desktop file like "/usr/bin/chromium-browser --profile-directory=Default --app-id=<app id in here>"
What is the expected result?
Chromium should either start the app (but it can't in incognito mode), or at least display a warning popup or console message about the reason why it won't create any window. (Something like app not found, or refusing to launch app in incognito mode, or both?).
What happens instead of that?
Chromium just sits there, doing nothing and making the impression that something is broken (as nothing happens, not even a warning).
UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/49.0.2623.108 Chrome/49.0.2623.108 Safari/537.36
(By the way havent found out where a link in Apps-menu should have landed, can just find that .desktop file, but I guess thats another issue.)
,
Jun 1 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 10 2016
This issue has been moved once and is lower than Pri-1. Removing the milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||
►
Sign in to add a comment |
|||
Comment 1 by tkonch...@chromium.org
, May 16 2016Labels: M-52
Status: Untriaged (was: Unconfirmed)