Example: From By Name, click on Photometry & SEDs. Open the Table editor, click reset. This results in a page reload, the use is not longer looking at the selected tab. We'd like to isolate events to within the <div> passed to FireFly.

These issues no doubt arise from the way we are embedding tables into our own environment, that is into the JQuery UI tabs in pages served by our Drupal instance. I think these problems may well be resolved by understanding and isolating events within our stack. Note: I had to figure out how to do the same type of behavior with Data tables to fix the sort-on-filter problem (disable event bubbling). NED can help identify the nature of the event isolation necessary to use Firefly within a complicated software stack, which contribute to the robustness of Firefly and its documentation.

CogE: Jeff