Should we explore converting our reliance upon form api's '#ajax" to javascript methods? The end result might give a happier path for support / feature improvement as we wouldn't need to edit both php and javascript in order to establish / enable behaviors on our controls.
A concrete example of how this conversion could work can be seen in PreviewControlsForm::refereshCallback
on line 62 of PreviewControlsForm we wire the refresh button to the refreshCallback, but all the callback does is invoke the existing javascript method: refreshCallback
Why not have the entirety of the setup and usage of the method be in javascript?
Consider moving all JS-based event registration and logic to the JS side of things.
* Talk this over with Brian
* Move all the interaction events to JS, maybe it provides a vehicle to add more Drupal.Announce (specifically thinking about refresh)
Postponed
1.0
Code
Postponing. We have moved more things into pure JS in 2.1, but also still rely on Drupal's ajax. Doubtful that we'd want to change that in 2.x.