David Graham wrote:

--- Robert Leland <[EMAIL PROTECTED]> wrote:


Yes, This has been brought up many times over the last 3 years,
and probably has been implemented several times extending the Struts
tags.

I am not opposed to such a feature, and would support it,
though other committers might not.

The key argument against it is that it would transform the html tags into a non-standard
implementation. The html tags are ment to be a thin module aware layer over the browsers tags,
and nothing more. That is why we don't have a Calender tag or Date chooser tag.
Though I suppose if you really --knocked our socks off !-- with a spiffy


implementation it could
become part of Struts.

I believe since we still support Netscape 4.X series browsers, a read-only attribute has
not been added.



As you know, we don't support browsers we support standard specifications.


Yes, and the decisions on what specfication to support relies largely on what browsers are out there.
Since we last talked about this Mozilla 1.X has been released which supports the read-only attribute
so users on Unix systems can benefit from its use. Best of all large slow moving corporations, Goverments,
with Unix systems to support are moving Mozilla/Netscape 6.2 as a standard. So I it seems that having
this workaround isn't as needed as it once was.


Now if we could only get rid of all the JSP 1.1/Servlet 2.2 containers so struts can move to supporting
JSP 1.2/Servlet 2.3..


-Rob



The tags are coded to the XHTML 1.0 and HTML 4.01 standards which do
support a readonly attribute on input fields.  The <html:text> tag
supports a readonly attribute which seems to be the easiest way to
accomplish the requested feature.

http://jakarta.apache.org/struts/userGuide/struts-html.html#text







Reply via email to