After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 732606 - New Window action does not work for many apps
New Window action does not work for many apps
Status: RESOLVED DUPLICATE of bug 647105
Product: gnome-shell
Classification: Core
Component: overview
3.10.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2014-07-02 05:00 UTC by Michael Catanzaro
Modified: 2014-07-02 07:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael Catanzaro 2014-07-02 05:00:00 UTC 
* Right click an app in the dock that you currently have open
* Click New Window

Expected behavior: A new window opens, always.

Actual behavior: Apps using GtkApplication usually do not open a new window.

We should either remove New Window from this menu, sad as that would be, or else figure out a standard way for apps to communicate to the shell that they do or do not support new window (and implement that with GtkApplication). Seems like a property GtkApplication could expose over D-bus? [1] (And for anything that doesn't use GtkApplication, it's probably pretty safe to assume it will work.)

[1] https://wiki.gnome.org/Projects/GLib/GApplication/DBusAPI
Comment 1 Michael Catanzaro 2014-07-02 05:01:38 UTC 
I forgot to add: one option would be to check if the app has an action named app.new-window, which is pretty standard for implementing the New Window action. (New Window is required by the draft HIG to be the first item in the app menu.)  But that's a bit hacky.
Comment 2 Florian Müllner 2014-07-02 07:20:58 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 647105 ***