[
http://issues.apache.org/jira/browse/BEEHIVE-1163?page=comments#action_12459766
]
Carlin Rogers commented on BEEHIVE-1163:
----------------------------------------
Nate has a workaround using the <netui:anchor> to create the correct onClick,
and then using that onClick for the onChange in the select. It looks like...
<netui:anchor action="selectProperty" formSubmit="true"
tagId="selectPropertyAction"/>
<netui:select
onChange="document.getElementById(lookupIdByTagId('selectPropertyAction', this
)).onclick();" dataSource="actionForm.selectedPropertyId">
...
</netui:select>
Just an option for others until this enhancement is addressed.
> It would be nice to specifyan 'action' on the <netui:select> tag that would
> correspond to a form submit on an onChange event
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-1163
> URL: http://issues.apache.org/jira/browse/BEEHIVE-1163
> Project: Beehive
> Issue Type: Improvement
> Components: NetUI
> Affects Versions: 1.0.1
> Reporter: Nathan Olson
>
> The <netui:anchor> tag has an 'action' and 'formSubmit' attribute that used
> in conjuction, will submit the current form to an action that is different
> than that specified in the enclosing <netui:form> tag. This works well when
> needing to submit the form to an intermediate action and keep the rest of the
> form around. It would be nice to have something similar surrounding a
> <netui:select> tag. Here's a the use case I'm interested in;
> I have a form that has two select fields and a textArea. However, the two
> select fields are related, meaning that the value chosen in selectA then
> feeds the options within selectB. So, I would like an action to be called
> when the onChange event on selectA is called that will then update the values
> within selectB. However, I don't want to lose the entire form as the user
> may have input some value in the textArea. Then, when the user has filled
> the entire form, the action on the form itself is submitted and processed.
> I think there might be a workaround for this specific use case, but this is a
> simplification of what I'm actually trying to accomplish (I've got many
> inter-related select boxes with many other things within the form) and I
> think solving this use case with same scenario that is used for the
> <netui:anchor> tag would solve my complex use case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
