Upon further contemplation a extendedHTMLTagBody attribute might be more appropriate. So that you can instruct the tag bean to write what is supplied into the html tag. (IE <html:textarea property="description" cols="30" rows="2" extendedHTMLTagBody="myCustomAttribute='something' wrap='hard'" />. I don't care how many attributes you implement in a tag somebody somewhere will need to have something extra written to the HTML stream.
-----Original Message----- From: Nimmons, Buster [mailto:[EMAIL PROTECTED] Sent: Monday, February 09, 2004 3:41 PM To: 'Struts Users Mailing List' Subject: RE: how to specify HTML attribute when HTML Tag does not have cor rosp onding attribute Not sure about browser specific, but view the properties/attributes section of the MSDN dhtml developer reference there are well over 200 attributes or properties available. Granted this is for all object types but there is still a tremendous gap between what is available and ahat is supported. This is my first application in which I have utilized STRUTS, I have normally shied away from tags to generate HTML tags just for this reason. I figured STRUTS is mature enough that I should run into very few of these situations. Well, the very first tag on the very first page is a culprit. Now, I'm not against implementing the WRAP attribute but having an unsupportedAttribute would sure make life easier at times. -----Original Message----- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Monday, February 09, 2004 3:24 PM To: Struts Users Mailing List Subject: RE: how to specify HTML attribute when HTML Tag does not have cor rosp onding attribute > Fair enough... I'm thinking If I have to subclass and create > this attribute would there be any forseeable harm in making an > "unsupportedAttribute" and pass in the key/value pair combination > to be rendered (IE. <html:textarea unsupportedAttribute="wrap='hard'" > property="description" cols="30" rows="2"/>) that way I don't > have to go through this every time I need to use a new attribute. What happens if you need to use two unsupported attributes in a single tag? I'd just extend the tag and do it right... How many browser specific attributes are there? -- Wendy Smoak Application Systems Analyst, Sr. ASU IA Information Resources Management --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]