20101 2012-11-27 16:49:01 +0000 insufficient set of "Return value data type" values 2012-11-27 18:32:15 +0000 1 1 1 Unclassified webplatform.org infrastructure unspecified PC All NEW P2 normal --- 1 letmespellitoutforyou schepers komoroske team-webplatform-admin public-webplatform-bugs oldest_to_newest 78922 0 letmespellitoutforyou 2012-11-27 16:49:01 +0000 See http://docs.webplatform.org/wiki/dom/apis/document/getNamedFlows for example. The method returns a NamedFlowCollection object, which is not represented in the canonical list of possible return values (http://docs.webplatform.org/wiki/Property:Javascript_data_type). "DOM Node" is perhaps closest, but misleading, as NamedFlowCollection is more analogous to a dynamic NodeList. The guy who reviewed my content flagged it as incorrect. Suggest implementing as <datalist> to allow content authors to enter different values as needed, then add valid new data types to the datalist. 78923 1 komoroske 2012-11-27 16:55:37 +0000 In this case I think you should just add NamedFlowCollection to the list of canonical data types. As we go forward, we will get to a position where that list just gets way too darn big, but we aren't there yet. 78924 2 letmespellitoutforyou 2012-11-27 16:59:13 +0000 Looks like the real problem is that "getNamedFlows" is a method & thus a function object, but that's pedantic in context considering that almost everyone will call it as a method & expect the method's return value. 78925 3 letmespellitoutforyou 2012-11-27 17:11:11 +0000 Possible setup is a <select/> box for the existing fixed "canonical" list of object member data types. If the member is a function, enable a <datalist/> mechanism specifying a much wider set of possible method return values. 78933 4 komoroske 2012-11-27 18:21:02 +0000 I'm not sure I follow comment #2. getNamedFlows is a method that returns a NamedFlowCollection object. NamedFlowCollection isn't an option in that part of the form because it's not on http://docs.webplatform.org/wiki/Property:Javascript_data_type (which is how that part of the form is generated). It should thus be added to that configuration page so it can be specified as the return value for getNamedFlows. Also, Semantic Forms is unfortunately somewhat limited in what types of form fields we can have. We (basically) get either a <select> or a free-form text field. 78934 5 letmespellitoutforyou 2012-11-27 18:32:15 +0000 OK, misunderstood "canonical" in this context. Also forgot I already submitted this as bug# 20005. Too bad the forms aren't more configurable.