JupyterWidgetView rendered twice on initialization

[dorisjlee]

This is traced back to internal calls in backbone.js and extension.js for create_view (which is called twice), leading the JupyterWidgetView class to be initialized twice.

export class JupyterWidgetView extends DOMWidgetView {

  initialize(){    
        ....
       ReactDOM.render(App,$app);
       view.el.append($app);
  }

It is unclear if this is an issue with the ipywidget internal or something different we have to do in our JupyterWidgetView react class (perhaps wrapping it in something other than initialize?).

Action Items:
For now, the logger accounts for this by de-duplicating initWidget events that occur together in too short a timespan.
We should look into this issue closer since this may cause a slowdown as the widget frontend needs to render two times.

[jacquekang]

It seems as though this issue is in the backend as you can see the widget get rendered twice in the console (pressing f12) and seeing that the widget objects in both render attempts are the same. However, there is still a possibility the problem is in the frontend from the way we initialize our widget.

In the backend, in (https://github.com/lux-org/lux/blob/master/lux/core/frame.py), if you get rid of self.output, in on_button_clicked, and display the widget directly onto whatever the output area of repr_html is, the widget actually renders once. The caveat is that since you are displaying directly to the output area of repr_html, you cannot access this area outside of repr_html. Or I couldn't find a way to refresh the widget in the backend when setting intent from the frontend. I'm not exactly sure why this is the behavior but the answer may lie in the internals of the output widget and its interactions with repr_html?