- 
    Suggestion 
- 
    Resolution: Won't Do
- 
    P2: Important 
- 
    6.4.1
- 
        fc3e9ec77 (dev), 3a8022c68 (6.9), f0ee80397 (6.9), 892c0c215 (6.9), 998a2a0a3 (6.9), bf7ca506a (6.8), 43e863088 (6.8), a1059f508 (6.8), 778386987 (6.8), e8548b04c (tqtc/lts-6.5), 254a5a6c0 (tqtc/lts-6.5), 39c13446b (tqtc/lts-6.5), 7e3967c97 (tqtc/lts-6.5)
This bug results from QTBUG-108612.
QtWebEngine uses foreign types in form of:
namespace ForeignWebEngineCertificateErrorNamespace
{
    Q_NAMESPACE
    QML_FOREIGN_NAMESPACE(QWebEngineCertificateError)
    QML_NAMED_ELEMENT(WebEngineCertificateError)
    QML_ADDED_IN_VERSION(1, 1)
    QML_EXTRA_VERSION(2, 0)
}
which is used for example like:
var handleCertificateError = function(error) { if (deferError) error.defer() else if (acceptCertificate) error.acceptCertificate() else error.rejectCertificate() } view.certificateError.connect(handleCertificateError)
The issue that QWebEngineCertificateError has only a copy constructor , but it is used here as value type. This is not correct as value types should have a default constructor. We do not want to use anonymous qml elements as our classes need proper documentation, therefore qml elements have to stayed named.
Instead we would like to use a value type which is QML_UNCREATABLE which would mean it can not be used as a property and it does not have a default constructor.
property webEngineCertificateError myError
This way we have value proper semantic , with value not instanceable by user , passed (copied) in various signal handlers.
- is required for
- 
                    QTBUG-108612 Startup warnings "... You should not use it as a QML type" -         
- Closed
 
-         
- 
                    QTBUG-110795 [Reg? 6.2.7 -> 6.4.2] New warnings in QtWebEngineQuick -         
- Closed
 
-         
- resulted in
- 
                    QTBUG-135032 Uncreatable value types behave erratically -         
- Closed
 
-