DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14071>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14071 Need clear info on which Struts attributes produce specific HTML attributes Summary: Need clear info on which Struts attributes produce specific HTML attributes Product: Struts Version: Nightly Build Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Documentation AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] It's amazing how often I read notes on "struts-user" asking why you can't set the "id" attribute in HTML tags with Struts. After taking a step back and looking at the documentation from this point of view, I guess I shouldn't be surprised. The documentation for the "styleId" attribute says: Identifier to be assigned to this HTML element. [RT Expr] As the resulting "id" attribute has meaning and context OUTSIDE of Struts, it's critical that we make this information clear. I'd like to suggest two things: 1. For all attributes which have some real use or intent outside of Struts (styleId, styleClass, style, and others), our documentation should clearly indicate what Struts attributes translate to those HTML attributes, if the names are not identical. This would translate to adding a little more information to the attribute description in the "struts-*.xml" (and "struts-*-el.xml") files, and a paragraph or two in the top-level user guide mentioning these mappings. 2. In the developing "FAQ" part of the user guide, a paragraph describing these mappings would be useful. -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
