Fixed create application shortcuts on Windows/Linux.

chrome/browser/ui/views/create_application_shortcut_view.cc

Index: chrome/browser/ui/views/create_application_shortcut_view.cc
diff --git a/chrome/browser/ui/views/create_application_shortcut_view.cc b/chrome/browser/ui/views/create_application_shortcut_view.cc
index 6361d207a4d3ecf1aef86ccb9ce8236b53f71508..2f462b2f757aa59500a3e8645b270ad717a2e9ff 100644
--- a/chrome/browser/ui/views/create_application_shortcut_view.cc
+++ b/chrome/browser/ui/views/create_application_shortcut_view.cc
@@ -391,10 +391,9 @@ bool CreateApplicationShortcutView::Accept() {
   creation_locations.in_quick_launch_bar = false;
 #endif
 
-  web_app::CreateShortcutsWithInfo(web_app::SHORTCUT_CREATION_BY_USER,
-                                   creation_locations,
-                                   shortcut_info_,
-                                   file_handlers_info_);
+  web_app::CreateNonAppShortcut(web_app::SHORTCUT_CREATION_BY_USER,

[tapted, 2014/12/22 00:05:09]

This doesn't look right. The profile and extension should exist here as well.
The issue in crbug.com/443882 seems to be that the extension is disabled,
whereas CreateShortcutsWithInfo only asks the extension registry for enabled
extensions.

I think options are to:
 a) Disable [gray-out] the `Create shortcuts` button on the app info dialog if
the extension is disabled
 b) Just change CreateShortcutsWithInfo to allow shortcut creation for disabled
extensions. The extension will get auto-enabled if the extension is clicked,
which is a bit weird, but it would restore the old behaviour.

[mitchellj, 2014/12/22 00:32:23]

I think option b) here is probably the easiest for now. I've made it to check
ExtensionRegistry::EVERYTHING.

+                                creation_locations, shortcut_info_,
+                                file_handlers_info_);
   return true;
 }