Title:
Bug 76937:(Watson Migration Closure)Add Generic Initialisation Params Argument to all AJAX UI Components
| View in TrackerStatus/Resolution/Reason: Closed/Won't Fix/
Reporter/Name(from Bugbase): Ben Davies / Ben Davies (Ben Davies)
Created: 04/30/2009
Components: AJAX, UI Components
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Normal / Unknown
Locale/System: English / Platforms All
Vote Count: 3
Problem:
Add Generic Initialisation Params Argument to all AJAX UI Components
As mentioned in various threads or bugs or enhancement requests, there are a number of Ext 2.0 widget options CF does not support directly via attributes. These options are usually set on the widget initialisation call in Ext, and cannot be set afterwards. This means that there is *no way* to use javascript to modify these options after the fact (a common suggested workaround).
A suggested approach for developers to be able to set the Ext settings is to include a single additional attribute on all CF ajax ui component tags that allows a struct to be passed to the underlying Ext JS call. Others supported attributes on the tag would override the values in the struct (if conflicting).
The benefit of this approach is that more of Ext can be leveraged without adandoning the CF AJAX UI tags and the benefits of easy data-binding etc. In fact many more requirements will be possible with no javascript at all.
Example usage:
<cfwindow title="my window" extparams="{'extparamname1':extparamvale1}">
Method:
Result:
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3038400
External Customer Info:
External Company:
External Customer Name: Ben Davies
External Customer Email: 447227C844C7765A992015A8
External Test Config: 04/30/2009Attachments:
Comments: