[
https://issues.apache.org/struts/browse/STR-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44543#action_44543
]
[EMAIL PROTECTED] edited comment on STR-2810 at 8/9/08 4:48 PM:
--------------------------------------------------------------
There has always been strong opposition to non-standard attributes and this is
the only case that seems to have been accepted as an exception. I don't see any
consensus on STR-2502 for a solution, but if it was thru' nested tags then
theres still benefit having this since its far simpler to use an attribute than
nested tags.
was (Author: [EMAIL PROTECTED]):
There has always been strong opposition to non-standard tags and this is
the only case that seems to have been accepted as an exception. I don't see any
consensus on STR-2502 for a solution, but if it was thru' nested tags then
theres still benefit having this since its far simpler to use an attribute than
nested tags.
> 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.
