Thanks, but actually, without wishing to cause offence, no thanks, please see below for why ...
On Tuesday, 16 June 2020 21:47:14 UTC+1, Paul Irish wrote: > > Hi, > > I'm sorry this broke you. I personally agree it doesn't make sense to > redirect the loader url to a new one that doesn't have backwards > compatibility. > There's no question of backwards compatibility here, because the 'new loader' is not actually a 'loader' as such! As I've now discovered, it's an entirely DIFFERENT script, it's actually the Google Visualisation API, which I don't even use! According to Google's own documentation, the loader that's been redirected is actually CURRENT, so this change has broken compliance with Google's own documentation! For proof, please see the following, which is a current page with a 2020 date ... https://support.google.com/code/answer/74501?hl=en ... so this change doesn't seem to be intentional, but an error by someone or other, which needs to be rolled back asap. > As for your particular situation... I tried to fix your webapp. Basically > it involves removing the loader. > I've written up a diff that fixes things: > https://gist.github.com/paulirish/a9d67166c91ab390d9585155b15be8de > > a few notes: > > 1. The 'search' API isn't supported at all by the new loader. > > That's because the 'new loader' is not actually a 'loader' as such, it's something entirely different, see above. > > 1. But also 1) i'm not sure it's supported by Google at all any longer > > According to Google's own documentation, it is, see above. > > 1. ... and 2) I don't think your webapp uses the API anymore. > > Of course it uses the Google Search Web API, otherwise I wouldn't be cluttering up my page by bothering to load it. What happens is that if either a user chooses a world place name search in the form, or attempts to use an old discontinued UK postcode which isn't found by querying UK Ordnance Survey, then Google Search is queried for the co-ordinates. > > 1. So I just removed the calls to attempt to use it. > > That's not going to help users of either page who live outside the UK. > > 1. This would almost work but the callback parameter handling in the > new loader doesn't work if the loader isn't the last <script> in the DOM. > (And in your case, it's the first). > 2. If the callback were good, we'd be in business, but there's a > console message about loading the maps API via the loader being > deprecated. > So I figure let's just drop the loader entirely. > 3. So that's what you'll see in the diff, we dynamically load the maps > API and drop loader/search entirely. > > I get the impression that you don't understand how my page loads. See the console log below. > Good luck > By uncommenting some debug lines in the original source, the following console log output is obtained. You can see from it that the *ONLY* problem is Google's inappropriate redirection of the loader script to an entirely different one that was never intended to have the same functionality. As this goes against Google's own current documentation, and is clearly an error by someone, it needs to be rolled back asap: Loading Google AJAX Loader ... SatelliteCalculator.shtml:216:2 DOMRdy:false, GSrchRdy:false, WMM:false, UKOSReqRdy:false, Proj4Rdy:true, Sats:true, Rotors:true, IningCalc:false SatelliteCalculator.shtml:346:2 DOMRdy:false, GSrchRdy:false, WMM:false, UKOSReqRdy:true, Proj4Rdy:true, Sats:true, Rotors:true, IningCalc:false SatelliteCalculator.shtml:346:2 DOMRdy:false, GSrchRdy:false, WMM:true, UKOSReqRdy:true, Proj4Rdy:true, Sats:true, Rotors:true, IningCalc:false SatelliteCalculator.shtml:346:2 Google AJAX Loader ready: 502ms SatelliteCalculator.shtml:210:2 Loading Google Search ... SatelliteCalculator.shtml:211:2 Document ready: 518ms SatelliteCalculator.shtml:340:2 DOMRdy:true, GSrchRdy:false, WMM:true, UKOSReqRdy:true, Proj4Rdy:true, Sats:true, Rotors:true, IningCalc:false SatelliteCalculator.shtml:346:2 Error: Module "search" is not supported. loader.js:93:451 -- -- You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group. To post to this group, send email to google-ajax-search-api@googlegroups.com To unsubscribe from this group, send email to google-ajax-search-api+unsubscr...@googlegroups.com To view this message on the web, visit https://groups.google.com/d/msgid/google-ajax-search-api/74d40f38-7800-4ca2-8e73-fa81864e8aa5o%40googlegroups.com For more options, visit this group at http://groups.google.com/group/google-ajax-search-api?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-ajax-search-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-ajax-search-api/74d40f38-7800-4ca2-8e73-fa81864e8aa5o%40googlegroups.com.
