1. All boolean attributes need to go back to minimized form
<select multiple> instead of <select multiple="mulitple">
This is currently implemented incorrectly anyways because in xhtml it
should be <select multiple="true">
2. Remove the ending / in <input> tags.
Here's my view:
- Forget xhtml in 1.1
- In 1.2 add a global configuration parameter that tells all html tags to emit xhtml (default to off). I don't care where this global param. goes but I do care that it be global and not dependant on using <html:html> or setting it on a tag by tag basis. I think a separate xhtml library of struts tags is going overboard.
Having said that, the whole point of xhtml is that it's valid xml webpages that all browsers can read. Yes, people could be using other clients besides browsers but those are probably few. I'm personally not worried about xhtml breaking backwards compatibility but do understand that others are. So, I think the solution suggested above is a decent compromise.
Comments?
David
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
Reply-To: "Struts Developers List" <[EMAIL PROTECTED]>
To: Struts Developers List <[EMAIL PROTECTED]>
Subject: Re: HTML, XML, XHTML and <html:html>
Date: Tue, 22 Oct 2002 11:57:52 -0700 (PDT)
On Tue, 22 Oct 2002, David Graham wrote:
> Date: Tue, 22 Oct 2002 11:19:57 -0600
> From: David Graham <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: HTML, XML, XHTML and <html:html>
>
> AFAIK, the only change is the closing / added to struts input tags. All
> browsers support this for reasons mentioned previously.
>
> I guess I just don't see how this is a serious change and how existing apps
> behavior would change. In my experience, over 95% of clients use Netscape
> 4.x+ or IE which both support this grammar. Many other people use Opera
> which also supports this.
>
You seem awfully confident that you know what client devices and programs
are being used by all Struts apps :-). It also goes totally against the
grain of how Struts enhancements have always been implemented -- leave the
default behavior the same as the previous version, and enable the new
feature with a parameter of some sort.
Let me say this more clearly:
-1 on unconditionally changing the output to emit the "/".
+0 on making this behavior dependent on xhtml="true" in the
outermost <html:html> tag.
> Dave
Craig
--
To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
_________________________________________________________________
Unlimited Internet access for only $21.95/month. Try MSN! http://resourcecenter.msn.com/access/plans/2monthsfree.asp
--
To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>