Two examples pointed out by lrbalt in #442 are when editing projects or contexts on their respective listing pages: the spinner never stops spinning.

In terms of development approach, I think what we should do here is remove the global spinner hide/show in application.js and make specific Ajax calls show the spinner and hide it. We may need to keep a count of shows vs. hides to support multiple overlapping operations.

Updating tickets (#373, #105, #107, #117, #125, #126, #147, #177, #182, #183, #185, #197, #202, #206, #220, #236, #240, #276, #283, #294, #300, #305, #309, #312, #317, #324, #337, #357, #358, #360, #433, #452, #462, #17, #74, #82, #92, #123, #265, #431, #440, #475, #94, #256, #258, #464)

Updating tickets (#743, #752, #768, #781, #535, #47, #295, #298, #805, #806, #324, #584, #97, #592, #344, #603, #114, #629, #636, #645, #393, #405, #433, #434, #202, #462, #220, #233, #310, #95, #635, #397, #94)

closing because ajax now always uses visual clues