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 765163 - Properly support the new-style built-in full screen mode of Mac OS X (version 10.7 and later)
Properly support the new-style built-in full screen mode of Mac OS X (version...
Product: GIMP
Classification: Other
Component: User Interface
git master
Other Mac OS
: Normal enhancement
: 3.0
Assigned To: GIMP Bugs
Depends on:
Reported: 2016-04-16 23:38 UTC by Kristian Rietveld
Modified: 2018-05-24 16:18 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Kristian Rietveld 2016-04-16 23:38:36 UTC
We need support in GTK+ for the fullscreen mode that is found in OS X versions 10.7 and later. If this support is there, we need to make GIMP play well with this and then remove the currently "old-style" fullscreen mode available through "View > Fullscreen".
Comment 1 Jehan 2017-01-04 13:44:25 UTC
If not in GTK+2, is this available in GTK+3? If so, I wonder if we cannot just push this to GIMP 3. Or should this absolutely be available for 2.10?
Comment 2 Kristian Rietveld 2017-01-05 21:44:23 UTC
I don't think proper support is available in GTK+3 either.

I don't consider this a 2.10 blocker. It's nice to get right if we have the time, but otherwise there are more pressing issues to address first.
Comment 3 Jehan 2017-03-24 23:27:42 UTC
I am trying to make some cleaning in the 2.10 bug list to make the path to the release cleaner. Are you planning pn working on this? Or should I just bump the report milestone to 3.0?
Thanks. :-)
Comment 4 Kristian Rietveld 2017-03-26 15:00:05 UTC
Likely 3.0 material, is it probably going to require to patches to GTK+ as well.
Comment 5 GNOME Infrastructure Team 2018-05-24 16:18:10 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: