If available, Qt WebEngine tries to use the system nss library for both SSL/crypto, and certificate handling. This has been causing problems, see e.g.
QTBUG-52068 , QTBUG-51890 .

Upstream chromium meanwhile has been moving towards always using the bundled BoringSSL for Crypto/SSL, and using NSS only for certificate handling:

https://groups.google.com/a/chromium.org/forum/#!searchin/chromium-dev/nss|sort:date/chromium-dev/HDqrFYlj7rE/0g6jKwt8uVkJ

This might mean that the NSS support for crypto might not get fixed, or even be removed in the future. We should decide whether we should invest time to fix this ourselves, or follow Chromium's lead to always rely on BoringSSL for crypto and NSS only for getting the system certificates.