JIRA 7.2 changed how customfield gets rendered using the `NEW_CONTENT_ADDED` event. It was a pain before but now, it is unmanageable and causes a lot of issues in IE/Edge and sometimes in Firefox (browser freeze). For a simple static field, rendering is completely done on server and it works fine. However, for fields having complex logic on the client side, it's not working at all.

Before 7.2, it was possible to apply different hacks. In 7.2 and beyond, freezing issues are unavoidable, especially since you started to be able to browse issues on the project view.
There is no solid and simple way (at least that I am aware of) to properly determine when your field is being rendered or discarded from the screen. In order to initialize my field on the client-side, I need to rely on JIRA.bind. One of the major problem is that as the user browse issues, I keep attaching watchers and I am never notified when the field is removed from the page so I cannot remove the watchers. This causes a multiplication of watchers which ends up freezing the browser. Also, sometimes, call backs do not get called in specific views (e.g. Dialogs).