This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20626 - Need a better way to specify non-primitive (or uncommon) return types
Summary: Need a better way to specify non-primitive (or uncommon) return types
Status: NEW
Alias: None
Product: webplatform.org
Classification: Unclassified
Component: default (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: public-webplatform-bugs list
QA Contact: public-webplatform-bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-10 00:08 UTC by Scott Rowe
Modified: 2013-01-10 00:08 UTC (History)
2 users (show)

See Also:


Attachments

Description Scott Rowe 2013-01-10 00:08:14 UTC
In the Basic property configuration form, for the Return value data type field you specify the data type of the object by selecting it from the drop-down menu. However, if the type is not in the list, you must edit the Property:Javascript_data_type and add the data type to the list.

The problems with this are, 1 - keeping the list in some order that makes sense (alphabetical), and 2 - dealing with a potentially endless list of types. 

We need to come up with a better way of specifying the type if it is not one of the primitive types. Perhaps an additional text input field under the drop-down where you can specify the type if you choose "Other" from the drop-down. The "Other" type would not be persistent, but defined for the page.