The feature "core.util.onload" makes a javascript call to gadgets.util.attachBrowserEvent(…), which is defined in the feature "core.util.event".
But, the onload feature doesn't have a dependency on the event feature, which means its javascript might execute before the attachBrowserEvent function has been declared. This happens in our container. I'm guessing it doesn't happen in shindig due to alphabetical sorting or some other shuffling that causes the event feature to come before onload. The fix is pretty straightforward. Just for grins, I'll attempt to attach a screenshot of a dev tool I wrote that displays the dependencies between some of shindig's features (modified to address this issue). -Randy Hudson
