We had a similar issue and I first thought it's the same. However, since you say it's remote content out solution probably does not apply to you. I'll post it here anyway for other people following.
We had to provide paths (to local files) on windows with forward slashes to get it to work again. Before file://C:\some\path\index.html After: file:///C:/some/path/index.html Regards Matthias On 12/13/18 12:34 PM, Tom Chadwin wrote: > The only other thing I'd check (but this is not a change from 3.2 to 3.4) is > that you are using QgsNetworkAccessManager, to tolerate any upstream proxy > issues. Beyond that, you'd have to check the logs of the webserver which > holds the JS, to see what's happening there. > > Tom > > > > ----- > Buy Pie Spy: Adventures in British pastry 2010-11 on Amazon > -- > Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-Developer-f4099106.html > _______________________________________________ > QGIS-Developer mailing list > [email protected] > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer > -- Matthias Kuhn [email protected] <mailto:[email protected]> +41 (0)76 435 67 63 <tel:+41764356763> OPENGIS.ch Logo <http://www.opengis.ch>
_______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
