In our experience with Internet Explorer, we often come across a problem where our 'create' controller attempts to format agility widgets using properties such as width(), position(), etc. A quick fix is to append the object to the DOM, and then run the configuration requiring those properties by triggering a controller. However, this breaks our widget encapsulation. The solution is to provide hooks for before and after the object is appended in order to complete any type of configuration. This way, the users of the widget won't forget to manually trigger controllers and the widgets will work as intended.
In our experience with Internet Explorer, we often come across a problem where our 'create' controller attempts to format agility widgets using properties such as width(), position(), etc. A quick fix is to append the object to the DOM, and then run the configuration requiring those properties by triggering a controller. However, this breaks our widget encapsulation. The solution is to provide hooks for before and after the object is appended in order to complete any type of configuration. This way, the users of the widget won't forget to manually trigger controllers and the widgets will work as intended.