<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[QFontDialog on macOS 27 isn&#x27;t modal anymore]]></title><description><![CDATA[<p dir="auto">The documentation for <code>QFontDialog</code> in Qt Widgets 6.12 says that it operates the dialog modally.</p>
<p dir="auto">In macOS 27, the (OS-native) font dialog lost its <strong>OK</strong> and <strong>Cancel</strong> buttons, so it's sort of non-modal now.  Our code (compiled in Qt 6.10.3) continues to block on the <code>QFontDialog::getFont</code> call as it did in macOS 26 and earlier when the dialog was fully modal, so the user must close the font dialog to continue, and the <code>ok</code> value on return is always <code>false</code>.</p>
<p dir="auto">I understand that there is a <code>currentFontChanged</code> signal we could use, and there's also the <code>DontUseNativeDialog</code> option to use the Qt (non-OS-native) font dialog instead, but it looks to me like <code>QFontDialog</code> is now behind the times with respect to macOS, so the Qt API or at least its documentation needs an update.</p>
<p dir="auto"><img src="https://ddgobkiprc33d.cloudfront.net/613952ff-8b57-4f0f-a038-cd4177a14344.png" alt="e59d7b71-7602-4385-a381-43564b8acbf6-image.png" class=" img-fluid img-markdown" /></p>
]]></description><link>https://forum.qt.io/topic/165172/qfontdialog-on-macos-27-isn-t-modal-anymore</link><generator>RSS for Node</generator><lastBuildDate>Thu, 05 Nov 2026 10:44:54 GMT</lastBuildDate><atom:link href="https://forum.qt.io/topic/165172.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 13 Oct 2026 18:48:15 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to QFontDialog on macOS 27 isn&#x27;t modal anymore on Wed, 28 Oct 2026 11:11:53 GMT]]></title><description><![CDATA[<p dir="auto">Classic macOS breaking platform consistency again. We ran into the exact same issue after updating our build machines — calling the static QFontDialog::getFont basically turns into a dead end because the native panel now behaves more like an inspector rather than a traditional modal dialog. Setting the QFontDialog::DontUseNativeDialog flag is pretty much the only sane workaround right now if you rely on blocking modal flow with OK/Cancel, even though the Qt-rendered dialog looks noticeably out of place on newer macOS versions.</p>
]]></description><link>https://forum.qt.io/post/840626</link><guid isPermaLink="true">https://forum.qt.io/post/840626</guid><dc:creator><![CDATA[TowMichal14]]></dc:creator><pubDate>Wed, 28 Oct 2026 11:11:53 GMT</pubDate></item><item><title><![CDATA[Reply to QFontDialog on macOS 27 isn&#x27;t modal anymore on Thu, 22 Oct 2026 19:15:21 GMT]]></title><description><![CDATA[<p dir="auto">I am using this as a replacement for  QFontDialog::getFont(), for now:</p>
<pre><code>QFont getFontFromDialog( bool* ok, const QFont&amp; font, QWidget* parent )
{
    Q_ASSERT( ok );
    QFontDialog::FontDialogOptions options;
#ifdef Q_OS_MACOS
    if ( QOperatingSystemVersion::current() &gt;= QOperatingSystemVersion( QOperatingSystemVersion::MacOS, 27 ) )
    {
        // native font dialog does not work with Qt for macOS 27
        options |= QFontDialog::DontUseNativeDialog;
    }
#endif
    QFont f = QFontDialog::getFont( ok, font, parent, QString(), options );
    return f;
}
</code></pre>
<p dir="auto">But I hope we get a fix so that we can use the new macOS 27 native font menu.</p>
]]></description><link>https://forum.qt.io/post/840575</link><guid isPermaLink="true">https://forum.qt.io/post/840575</guid><dc:creator><![CDATA[AndyBrice]]></dc:creator><pubDate>Thu, 22 Oct 2026 19:15:21 GMT</pubDate></item><item><title><![CDATA[Reply to QFontDialog on macOS 27 isn&#x27;t modal anymore on Thu, 15 Oct 2026 10:29:53 GMT]]></title><description><![CDATA[<p dir="auto">Indeed. I filed <a href="https://qt-project.atlassian.net/browse/QTBUG-151608" target="_blank" rel="noopener noreferrer nofollow ugc">https://qt-project.atlassian.net/browse/QTBUG-151608</a> on the matter.</p>
]]></description><link>https://forum.qt.io/post/840498</link><guid isPermaLink="true">https://forum.qt.io/post/840498</guid><dc:creator><![CDATA[IgKh]]></dc:creator><pubDate>Thu, 15 Oct 2026 10:29:53 GMT</pubDate></item><item><title><![CDATA[Reply to QFontDialog on macOS 27 isn&#x27;t modal anymore on Wed, 14 Oct 2026 23:45:20 GMT]]></title><description><![CDATA[<p dir="auto">Minimal compilable example, based on Qt Creator's "Qt Widgets Application":</p>
<pre><code>#include "mainwindow.h"
#include &lt;QtWidgets/QFontDialog&gt;

MainWindow::MainWindow(QWidget *parent)
    : QMainWindow(parent)
{
    bool ok = false;
    QFont font = QFontDialog::getFont(&amp;ok, this);
    qDebug() &lt;&lt; "ok =" &lt;&lt; ok &lt;&lt; "font =" &lt;&lt; font;
}

MainWindow::~MainWindow() = default;
</code></pre>
<p dir="auto">Result under macOS 27, regardless of what font is selected in the Apple font dialog, after closing the dialog using the red button:</p>
<pre><code>ok = false font = QFont(.AppleSystemUIFont,13,-1,5,400,0,0,0,0,0,0,0,0,0,0,1)
</code></pre>
<p dir="auto">In macOS 26, this same code would have set <code>ok</code> to <code>true</code> and <code>font</code> to whatever was selected, after the user clicked the <strong>OK</strong> button that is no longer visible in macOS 27 (as the other commenter described).</p>
]]></description><link>https://forum.qt.io/post/840494</link><guid isPermaLink="true">https://forum.qt.io/post/840494</guid><dc:creator><![CDATA[barbicels]]></dc:creator><pubDate>Wed, 14 Oct 2026 23:45:20 GMT</pubDate></item><item><title><![CDATA[Reply to QFontDialog on macOS 27 isn&#x27;t modal anymore on Wed, 14 Oct 2026 16:49:22 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/barbicels">@<bdi>barbicels</bdi></a> Qt's implementation makes some assumptions about the internal structure of <code>NSFontPanel</code> (AppKit's native font selector) to inject the action buttons into it. They are not a built-in option. This likely broke with macOS changes. I don't see an open ticket in the bug tracker about it - I encourage you to create one, with the minimal reproducer.</p>
]]></description><link>https://forum.qt.io/post/840490</link><guid isPermaLink="true">https://forum.qt.io/post/840490</guid><dc:creator><![CDATA[IgKh]]></dc:creator><pubDate>Wed, 14 Oct 2026 16:49:22 GMT</pubDate></item><item><title><![CDATA[Reply to QFontDialog on macOS 27 isn&#x27;t modal anymore on Tue, 13 Oct 2026 19:01:26 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">Can you provide a minimal compilable example that shows this behaviour change ?</p>
]]></description><link>https://forum.qt.io/post/840482</link><guid isPermaLink="true">https://forum.qt.io/post/840482</guid><dc:creator><![CDATA[SGaist]]></dc:creator><pubDate>Tue, 13 Oct 2026 19:01:26 GMT</pubDate></item></channel></rss>