Details
Description
Currently, there doesn't appear to be a way to specify which type of root node will be used for instantiating a customDijit. I believe the default is a <div>, but for semantic reasons it might be better to specify a custom element type to ensure a page could degrade gracefully.
My example would be a custom multiselect from dojox. It doesn't require a <select> element to be the root, but <div><option></option></div> isn't valid markup and could have unpredictable results (nor would it degrade). (Note: the issue doesn't exist if you are using a datastore with this widget, as all markup instantiation is done for you, but the overall implication would suggest having a root node setting would be best, hence this ticket)
You can now pass 'rootNode' as one of the params to a customDijit; ability added in trunk and merged to 1.9 release branch.