turns out my suspicion was correct.
the issue is tracked upstream at https://bugreports.qt.io/browse/QTBUG-87776 .
please re-open the bug and retitle it appropriately.

Reply via email to