diff options
| author | Danilo M. <danix@danix.xyz> | 2026-08-03 09:43:07 +0200 |
|---|---|---|
| committer | Danilo M. <danix@danix.xyz> | 2026-08-04 12:52:53 +0200 |
| commit | 2ca7ba8642e81e400a8f3145a15e3f6328b36a28 (patch) | |
| tree | c3a13b6238c411c8b965a5cdc652b6871e942a13 /tests/test_messageview.cpp | |
| parent | cf8edbf6bc5a3d9131fb095f573cbef70d61202e (diff) | |
| download | qtmaildir-2ca7ba8642e81e400a8f3145a15e3f6328b36a28.tar.gz qtmaildir-2ca7ba8642e81e400a8f3145a15e3f6328b36a28.zip | |
fix: render the message pane at all
Clicking a thread left the pane blank. Two independent bugs, both from the
same false premise: that setHtml() navigates to the base URL it is given.
It does not. setHtml() navigates to a data: URL carrying the markup and
applies the base URL afterwards, purely as the document's origin. Verified
empirically on Qt 6.11.
Built on that wrong assumption were:
- MessagePage::acceptNavigationRequest compared the navigation's URL
against documentUrl() and rejected everything else, so the document load
was refused. It now accepts a typed main-frame navigation, which is one
we initiated ourselves.
- RequestInterceptor exempted exactly the qtmaildir: base URL and denied
everything else, so the data: document load was blocked too.
The interceptor fix is scoped to ResourceTypeMainFrame rather than allowing
the data: scheme outright. A blanket allow would have been a real hole: a
message body can write <img src="data:..."> or an iframe, and the existing
dataSchemeBlocked test in test_interceptor.cpp was right to fail when that
was tried. Sub-resource data: URLs remain denied.
Note this was never working. The drafted version had the same defect in a
different spelling (it compared url.scheme() rather than the whole URL, and
would have rejected the data: navigation just the same), and task 11 shipped
with no runtime test to catch it. test_messageview.cpp now pins all three
facts: the document loads, its text reaches the page, and a data: image
inside a hostile body stays blocked.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Diffstat (limited to 'tests/test_messageview.cpp')
| -rw-r--r-- | tests/test_messageview.cpp | 161 |
1 files changed, 161 insertions, 0 deletions
diff --git a/tests/test_messageview.cpp b/tests/test_messageview.cpp new file mode 100644 index 0000000..261fec2 --- /dev/null +++ b/tests/test_messageview.cpp @@ -0,0 +1,161 @@ +#include <QSignalSpy> +#include <QWebEngineUrlScheme> +#include <QWebEngineView> +#include <QtTest> + +#include "htmlbuilder.h" +#include "messageview.h" +#include "mimeparser.h" + +/// MessageView needs a live QWebEngineProfile, so most of it is verified +/// manually. What is pinned here is the one thing that silently produced a +/// blank pane: whether a document handed to setHtml() actually loads. +class TestMessageView : public QObject +{ + Q_OBJECT +private slots: + void initTestCase(); + void documentActuallyLoads(); + void threadContentReachesThePage(); + void dataUrlSubResourceStillBlocked(); + +private: + QWebEngineView *webViewOf(MessageView *view) const + { + return view->findChild<QWebEngineView *>(); + } +}; + +void TestMessageView::initTestCase() +{ + // Registered in main() in the real application; a test binary has its own + // entry point and must do the same before any profile exists. + QWebEngineUrlScheme cid(QByteArrayLiteral("cid")); + cid.setFlags(QWebEngineUrlScheme::SecureScheme + | QWebEngineUrlScheme::ContentSecurityPolicyIgnored); + QWebEngineUrlScheme::registerScheme(cid); + + QWebEngineUrlScheme own(QByteArrayLiteral("qtmaildir")); + own.setFlags(QWebEngineUrlScheme::SecureScheme); + QWebEngineUrlScheme::registerScheme(own); +} + +void TestMessageView::documentActuallyLoads() +{ + // The regression this exists for: acceptNavigationRequest compared the + // navigation's URL against documentUrl(), but setHtml() navigates to a + // data: URL and applies the base URL only as the document origin. Every + // document load was rejected and the pane stayed blank, with no warning + // anywhere. + MessageView view; + QWebEngineView *web = webViewOf(&view); + QVERIFY(web); + + QSignalSpy loaded(web, &QWebEngineView::loadFinished); + + ParsedMessage message; + message.ok = true; + message.from = QStringLiteral("Alice <alice@example.org>"); + message.subject = QStringLiteral("Hello"); + message.date = QStringLiteral("Mon, 1 Jun 2026 10:00:00 +0000"); + message.plainBody = QStringLiteral("body text"); + + ThreadRenderItem item; + item.message = message; + item.cidPrefix = QStringLiteral("m0"); + item.expanded = true; + + view.showThread({ item }); + + QVERIFY2(loaded.wait(15000), "no loadFinished at all: the document was " + "never even attempted"); + QCOMPARE(loaded.size(), 1); + QVERIFY2(loaded.first().at(0).toBool(), + "loadFinished reported failure: the navigation was rejected"); +} + +void TestMessageView::threadContentReachesThePage() +{ + // Loading successfully is not the same as showing the message: assert the + // body actually made it into the rendered document. + MessageView view; + QWebEngineView *web = webViewOf(&view); + QVERIFY(web); + + QSignalSpy loaded(web, &QWebEngineView::loadFinished); + + ParsedMessage message; + message.ok = true; + message.from = QStringLiteral("Bob <bob@example.org>"); + message.subject = QStringLiteral("Subject line"); + message.plainBody = QStringLiteral("distinctive-body-marker"); + + ThreadRenderItem item; + item.message = message; + item.cidPrefix = QStringLiteral("m0"); + item.expanded = true; + + view.showThread({ item }); + QVERIFY(loaded.wait(15000)); + QVERIFY(loaded.first().at(0).toBool()); + + QString text; + bool done = false; + web->page()->toPlainText([&](const QString &result) { + text = result; + done = true; + }); + QTRY_VERIFY_WITH_TIMEOUT(done, 15000); + + QVERIFY2(text.contains(QStringLiteral("distinctive-body-marker")), + qPrintable(QStringLiteral("rendered text was: '%1'").arg(text))); + QVERIFY(text.contains(QStringLiteral("bob@example.org"))); +} + +void TestMessageView::dataUrlSubResourceStillBlocked() +{ + // The main-frame exemption must not extend to sub-resources: a message + // body can write <img src="data:..."> and those stay denied. This is the + // narrow line between "the document renders" and "the policy has a hole". + MessageView view; + QWebEngineView *web = webViewOf(&view); + QVERIFY(web); + + QSignalSpy loaded(web, &QWebEngineView::loadFinished); + + ParsedMessage message; + message.ok = true; + message.from = QStringLiteral("Mallory <mallory@example.org>"); + message.subject = QStringLiteral("Hostile"); + // A 1x1 gif as a data: URL, the shape a tracking-adjacent body would use. + message.htmlBody = QStringLiteral( + "<html><body>visible-text" + "<img id=\"probe\" src=\"data:image/gif;base64," + "R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7\">" + "</body></html>"); + + ThreadRenderItem item; + item.message = message; + item.cidPrefix = QStringLiteral("m0"); + item.expanded = true; + + view.showThread({ item }); + QVERIFY(loaded.wait(15000)); + QVERIFY2(loaded.first().at(0).toBool(), + "the document itself must still load"); + + // The document rendered; the blocked sub-resource is what the interceptor + // records. Text is present, so this is not a failed load masquerading as + // a blocked image. + QString text; + bool done = false; + web->page()->toPlainText([&](const QString &result) { + text = result; + done = true; + }); + QTRY_VERIFY_WITH_TIMEOUT(done, 15000); + QVERIFY(text.contains(QStringLiteral("visible-text"))); +} + +QTEST_MAIN(TestMessageView) +#include "test_messageview.moc" |
