elgg.ui.initDatePicker not initializing on ajax calls

[ismayil.khayredinov]

All methods in ui.js are live, aside from initDatePicker. If elgg.ui.init is called on ajax success, there are multiple problems with propagation. Perhaps it would be a good idea to separate live and bind methods, and ideally create a separate ui.init function for ajax calls.

[ewinslow]

The JS Framework is clearly still in its infancy. Handling ajax requests is still not really supported.

We need a standard way to provide initialization code that doesn't require the users to think about ajax or delegation or liveness or any of that. E.g...

elgg.ui.Datepicker.init = function(context) {
  // Only initialize *new* content (i.e. stuff in "context")
  $('.elgg-input-date', context).elggDatepicker();
};

// Run this callback on DOM ready and whenever new HTML is inserted into the page
elgg.fancyCallbackRegistrationThingy(elgg.ui.Datepicker.init);

[ismayil.khayredinov]

Any further thoughts on this?

[cash]

We need to come up with a solution that is general - like Evan described. That would be for Elgg 1.9.

For Elgg 1.8, we could come up with a special solution for this.

[ewinslow]

This is probably not going to happen for 1.9, but should happen soon.