You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Deepak Dixit (JIRA)" <ji...@apache.org> on 2011/04/30 11:15:03 UTC
[jira] [Commented] (OFBIZ-4267) Disabled attribute for lookup field
should be readonly.
[ https://issues.apache.org/jira/browse/OFBIZ-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027304#comment-13027304 ]
Deepak Dixit commented on OFBIZ-4267:
-------------------------------------
Thanks Ashish for committing the patch.
Thanks Rishi for the discussion.
> Disabled attribute for lookup field should be readonly.
> -------------------------------------------------------
>
> Key: OFBIZ-4267
> URL: https://issues.apache.org/jira/browse/OFBIZ-4267
> Project: OFBiz
> Issue Type: Bug
> Components: ALL COMPONENTS
> Affects Versions: Release Branch 10.04, SVN trunk
> Reporter: Deepak Dixit
> Assignee: Ashish Vijaywargiya
> Priority: Minor
> Fix For: Release Branch 10.04, SVN trunk
>
> Attachments: OFBIZ-4267-branch10.04.patch, OFBIZ-4267-trunk.patch
>
>
> Lookup tag has a attribute "disabled" that is used to set disabled="disabled" property for lookup input element and it create also a clear button just after lookup field to clear the field value.
> But if we set disabled="disabled" for any input field then that field does not passes as parameter and we can't accesses it from parameters or request parameters , so it should be "readonly".
> If we set readonly-"readonly" then user can't change the field value directly, and this field passes as parameters.
> Only difference between readonly and disabled is that in case of disabled field does not passes as parameter buy in case of readonly field passes as a parameter.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira