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
