[
https://issues.apache.org/struts/browse/WW-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Don Brown updated WW-2092:
--------------------------
Fix Version/s: (was: 2.0.11)
2.1.x
See: http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JSPTags4.html under dynamic
attributes. The question is whether this is a good idea or not. If you allow
dynamic attributes, it is harder for tools like idea to provide autocomplete
and validation. Stripes solves this by shipping two TLD's, one that allows and
one that doesn't.
> Update UI tags to allow custom html tag attributes
> --------------------------------------------------
>
> Key: WW-2092
> URL: https://issues.apache.org/struts/browse/WW-2092
> Project: Struts 2
> Issue Type: Improvement
> Components: Views
> Affects Versions: 2.0.9, 2.1.x
> Reporter: zhouyanming
> Assignee: James Holmes
> Fix For: 2.1.x
>
> Attachments: src.zip
>
>
> for example <input type="text" name="text" autocomplete="off"/> can't use
> <s:textfield name="test" autocomplete="off"/> because autocomplete is not
> valid for this jsp tag.
> I suggest add a new jsp tag attribute for all UI tags like this
> <s:textfield name="test"
> tagAttributes="#{'autocomplete':'off','onsuccess':'alert(\'success\')','onfailure':'alert(\'failure\')'}"/>
> tagAttributes is a map,and this tag result to
> <input type="text" name="text" autocomplete="off"
> onsuccess="alert('success')" onfailure="alert('failure')"/>
> also can add another attribute 'templateParameters',this attribute like
> 'tagAttributes',but it's used for custom freemarker template.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
