[
https://issues.apache.org/struts/browse/STR-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44542#action_44542
]
paul4christ79 edited comment on STR-2810 at 8/9/08 1:05 PM:
------------------------------------------------------------
I think we should change this a little bit. STR-2502 issue exists to allow
non-standard attributes through the use of a nested tag. The idea was that
non-standard attributes would not be allowed unless they were turned on at the
form level so people can be a little bit more inventive with Dojo or other
vendor specifics. Struts 2 is allowing this already: WW-2132. They added the
property "allowDynamicAttributes" and I believe we should do the same.
was (Author: paul4christ79):
I think we should change this a little bit. There's another issue slated in
1.4 to allow non-standard attributes through the use of a nested tag. The idea
was that non-standard attributes would not be allowed unless they were turned
on at the form level. Niall, I think we could change the FormTag property to
"allowNonstandard" to setup the future ?
> autocomplete attribute
> ----------------------
>
> Key: STR-2810
> URL: https://issues.apache.org/struts/browse/STR-2810
> Project: Struts 1
> Issue Type: Improvement
> Components: Tag Libraries
> Affects Versions: 1.3.1
> Environment: Operating System: other
> Platform: All
> Reporter: Mark Lowe
> Assignee: Niall Pemberton
> Priority: Minor
> Fix For: 1.3.10, 1.4.0
>
> Attachments: BaseInputTag.java.patch.java, FormTag.java.patch.java,
> struts-html.tld.patch
>
>
> the non standard attribute autocomplete cannot be deactivated (i.e.
> autocomplete="off" ) without
> subclassing the tag class itself and editing tld files, effectively forking
> from the struts code base.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
