Metadata
- Source
- FLUID-4534
- Type
- Bug
- Priority
- Major
- Status
- Closed
- Resolution
- Fixed
- Assignee
- N/A
- Reporter
- Anastasia Cheetham
- Created
2011-11-03T16:18:53.028-0400 - Updated
2013-08-16T10:54:32.847-0400 - Versions
-
- 1.4
- Fixed Versions
-
- 1.5
- Component
-
- UI Options
Description
Environments
The root UI Options component fires an event named "onUIOptionsComponentReady." From an integrator's perspective, the naming implies that the event will fire once the component is ready. In fact, this event is used to trigger the creation of various subcomponents (e.g. textControls, layoutControls, etc). It may fire when the internal UI Options component is technically ready for its subcomponents to be added, but it's not when "the component," as the integrator likely perceives it, is ready.
Perhaps what we need is a separate event fired by the uber-component (e.g. fatPanel) when the uber-component is, in fact, "ready" as an integrator would expect, that is: all subcomponents are finished rendering, everything is hooked up, and the component is ready to use.
Comments
-
Antranig Basman commented
2012-08-22T14:53:15.664-0400 With the resolution of FLUID-4257, it is now possible for people to subscribe to the standard "onCreate" event of UIOptions