The readonly-attribute can have the following two states
- readonly and - [nothing].
There is no readonly ="true" or readonly="false" for HTML text-input-fields.
(The same applies for the 'disabled'- and 'checked'-attributes of e.g. checkboxes)
For this reason the browsers behavior is correct. OK, maybe it's a little misleading (if you are used to boolean-variables in Java or any other programming language), but why specify
readonly="false"
when
"writable"
is the default anyway?
Bye,
Mario
-----Original Message-----
From: John Moore [mailto:[EMAIL PROTECTED]
Sent: Monday, May 03, 2004 4:07 PM
To: Struts Users Mailing List
Subject: RE: Setting html:text readonly attribute
I've found that this, unfortunately doesn't work, at least with my current browser of choice (Firefox), which insists on making the text field read-only as long as there is a 'readonly' attribute present. I'm exploring the other options next.
I have to say, completely off-topic, that it strikes me as pretty moronic behaviour for a browser if you have a boolean attribute, readonly, and it interprets "readonly='false'" as being an instruction to make the field read-only. But it does.
John
=============================================
John Moore - Norwich, UK - [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]
