Would have agreed with you if it had not worked for both the case. What was confounding was that it worked for one of the field and not for the other. I would assume "will not mess with the actual internal (to the browser) representation" that it would not mess at all. But it's messing.
-----Original Message----- From: Lobello Jeffrey [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 23, 2003 12:57 PM To: Shishir K. Singh; Pitchko, John SCAN--; Struts Users Mailing List Subject: RE: Html:input help Generally, CSS (such as text-transform) will alter the visual display/rendering of HTML, but will not mess with the actual internal (to the browser) representation. Thus, I would consider it 'correct' that 'text-transform: uppercase', when applied to an HTML input field with lowercase text in it, is not causing the submitted text to be converted to uppercase. For a more definitive answer, I would suggest rereading the CSS specs at http://www.w3c.org/. -----Original Message----- From: Shishir K. Singh [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 23, 2003 12:28 PM To: Pitchko, John SCAN--; Struts Users Mailing List Subject: RE: Html:input help That is what I resorted to ultimately (the dirty way I guess). The issue here is that the formatting of the attribute is dictated by a config file, saying which ones will be upper case and which ones will be lowercase. Hence I was initially trying with the CSS style attribute on html:input (text) tag to control the input. Here is what happens. When the user types in with the Caps Lock off, the entry is all uppercase but the value sent to the server is lowercase. However, the entry is uppercase if the user switches the caps lock on. This is what confused me. Even though the user sees the entries as all Uppercase (with caps lock off since the style defines text-transform: uppercase), the actual values are lowercase. I have resorted to doing a regex on the config variable (that I store on a bean) and explicitly set the form field value to uppercase if I find a matching pattern of "uppercase" in the config variable...yuck!!. But the css style attribute for html:input (text) completely buffoons me. Perhaps, inline css is not supposed to be used with html:input (text type) tag ?? -----Original Message----- From: Pitchko, John SCAN-- [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 23, 2003 9:02 AM To: Shishir K. Singh; Struts Users Mailing List Subject: RE: Html:input help IMO, you're probably better off doing this kind of data transformation inside of an Action. Would it be at all possible to do this within your application? -----Original Message----- From: Shishir K. Singh [mailto:[EMAIL PROTECTED] Sent: December 22, 2003 4:44 PM To: Struts Users Mailing List Subject: Html:input help Hi, I have two html:input (type text ) fields on my form and I am converting them to upper case using inline css style. I have included the rendered html page snippet. If you see, the PartNo retains the value uppercase value (TEST1). However, the Part Description is not correct even though the style is same. If I remove the Part No from the form, the Part description gets the correct value i.e all uppercase. Has anyone faced this problem ? If so, any advice would be appreciated. ------------------------------------------------------------------------ -- <tr> <td class="contentLeft"> Part No </td> <td class="contentRight"> <input type="text" name="lines[0].attrValue" maxlength="20" size="20" value="TEST1" style="text-transform: uppercase;" class="contentText"> </td> </tr> <tr> <td class="contentLeftCol"> Part Description </td> <td class="contentRight"> <input type="text" name="lines[1].attrValue" maxlength="64" size="50" value="fdsfdsfsdfdsf" style="text-transform: uppercase;" class="contentText"> </td> </tr> TIA Shishir ------------------------------------------------------------------------ ------- This message and any included attachments are from Siemens Medical Solutions USA, Inc. and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail with a copy to [EMAIL PROTECTED] Thank you --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
