True, it is features/core/legacy.js but given that this content is also licensed as open source (and included in current shinding development) I, as developer, do not see it as an immediate problem. Probably tickets could/should be raised against any apps relying in legacy.js and people should, at some time, fix it.
On the other hand, the question of legacy surfaces from time to time in the main list: http://groups.google.es/group/opensocial-api/browse_thread/thread/a0ab729ec75b03c2/2aec1adb658e0cd0 http://groups.google.es/group/opensocial-api/browse_thread/thread/9cc97a8ad18c230f etc 2008/3/21, Kevin Brown <[EMAIL PROTECTED]>: > On Fri, Mar 21, 2008 at 5:28 AM, Cassie <[EMAIL PROTECTED]> wrote: > > > The compliance tests work in the samplecontainer Kevin. They are perfectly > > fine. > > > > They work, yes (because we have a legacy mapping) -- but they're *not* spec > compliant. If you could show me the section of the spec where > _IG_RegisterOnLoadHandler is defined I'll retract that statement. > > -- > > ~Kevin >
