This one is really terrible. We experienced the same here and I might be able to partially point to the function that’s causing it. I noticed it when I was explaining something to a colleague at her workplace: she used osTicketAwesome (1.12-102) with Firefox and set in her account settings the refresh rate for ticket pages to “every minute”. In my account settings the refresh rate is deactivated. Anyway, I tried to show her some things and became very irritated about the same weird issue netwatch posted: a lot of buttons did not work – like they where freezed. After refreshing the whole page they worked again… worked… and suddenly they stopped working again. I started realizing that it happens after her ticket page refreshed. So I went to my workplace (chrome, firefox – both the same) and activated the refresh rate -> and yep, experienced the same. Always (not 100% sure if it’s really always) after the javascript refresh you can’t open any (modal) dialog anymore (for instance “edit current queue”).
ps: you can experience it in the demo as well. Just set the refresh rate to “every minute”, open ticket page, wait a minute until you see the refresh and try to open a modal dialog, for instance: try to edit the current queue.