Ok found the solution by myself. Obviously it's the definition of mime type that expect a slash between main and sub type and Qt5 is stricter with evaluation of mime types.
----- Ursprüngliche Mail ----- Von: "Frank Fischer | roomeon" <[email protected]> An: [email protected] Gesendet: Dienstag, 6. Mai 2014 18:37:03 Betreff: [webkit-qt] QWebPage unsupported content does not work Hi, I'm just updated from Qt 4.8.5 to Qt 5.2.1 and unfortunately forwarding of unsupported content in QWebPage does not work anymore. I've set forwardUnsupportedContent to true and I'm getting a reply with Content-Type="my_action". The content of the reply is xml based but I changed the Content-Type header by the server that delivers the reply. In 4.8.5 this always caused a call of the unsupportedContent signal but now the content of the WebPage gets fully grey and the Inspector gives me the XML-Content I wanted to handle by my Slot connected to unsupportedContent. Is it a bug or have I missed something? Best regards, Frank _______________________________________________ webkit-qt mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-qt _______________________________________________ webkit-qt mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-qt
