Matt Read wrote:
Sorry that I keep using the <br> tag as an example because I agree it's not
a particularly good, although it does demonstrate my point. I see a problem
not with the <br> tag in particular as obviously Struts taglibs don't
generate them, but that to be absolutely certain that there aren't any major
problems with older browsers and XHTML, we would have to run a very
comprehensive regression test on a significant number of browser/OS/version
combinations. As far as I know neither struts or the browser vendors have
the regression tests available for this.
I'm not arguing for or against :-) Just stating something I thought you
missed. I have to say that you make a very valid point though.
As much as I'd like to be able build sites that worked only in Mozilla 1.0
and IE6.0, my customers still feel that the minority browsers are important.
Until that trend finishes (I think we've got at least a year yet), I would
hate to be stalled on a particular version of struts when we could easily
make it a configurable option.
As Craig mentioned, that would be the way to do it. Make it optional -
default current behavior (off).
How about a compromise... instead of each tag having to be explicitly
configured, add a generic request processor configuration item in
struts-config.xml?
Can we save it for 1.2.x? :-) ... or is this something we've stated
would be in 1.1F and I'm just not familiar with it?
Matt.
--
Eddie Bush
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
