Of Mash-ups and Cock-ups
Traditionally, when writing code against third-party libraries, confidence in the interface between your code and the library would only increase over time. If you used the same stable release of a library and your code didn't change, you knew it would just keep working the same way.
Online services are different though, particularly "beta" or "labs" services like, say, Google Suggest.
I publish a Google homepage gadget which adds Google Suggest behaviour to your iGoogle homepage. It has been working beautifully for weeks now and I have quite a few users. And then, out of the blue, it stopped working. I haven't changed anything. FireBug is reporting errors in ac.js, the Javascript file which provides the Ajax Suggest behaviour.
Online services are different though, particularly "beta" or "labs" services like, say, Google Suggest.
I publish a Google homepage gadget which adds Google Suggest behaviour to your iGoogle homepage. It has been working beautifully for weeks now and I have quite a few users. And then, out of the blue, it stopped working. I haven't changed anything. FireBug is reporting errors in ac.js, the Javascript file which provides the Ajax Suggest behaviour.
window.google has no properties
http://www.google.co.uk/ac.js
Line 26
Comments