I think the CSS recommendation fit and pushed the JSTL tag, which would break an otherwise well formed TR tag, into an attribute value where it is less problematic--unless the editor in question tries to validate that the contents of the style tag are indeed valid CSS definitions. According to the last post from the OP, Dreamweaver stopped complaining when the JSTL was moved into the style attribute, so it is lenient enough to allow otherwise suspect characters there. Depending on what DTD is being used for the HTML, particularly any flavor of XHTML, having a "<" character in an attribute could still be illegal thus invalidating the TR tag, but Dreamweaver apparently isn't being that strict.
Thomas Gideon Sr. Software Developer B2eMarkets 301.230.2236 Tel. 301.230.2248 Fax. [EMAIL PROTECTED] www.B2eMarkets.com > -----Original Message----- > From: Dave Newton [mailto:dave@;solaraccess.com] > Sent: Tuesday, October 29, 2002 11:47 AM > To: Tag Libraries Users List > Subject: Re: JSTL making Dreamweaver unhappy. > > > > I actually use JSTL to write the attribute and value with > the tag for > > display purposes. > > [snipalufagus] > > <tr <c:out value='${bgColor}'/> align="center"> > > That's not the point; I think a previous poster was saying that the > reason the editor was barfing was that as written above you don't > have a valid table row tag! The editor doesn't know (does it?! If > so, then never mind!) how the tr tag it will be rendered on > the client. > > Dave > > > > -- > To unsubscribe, e-mail: > <mailto:taglibs-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: > <mailto:taglibs-user-help@;jakarta.apache.org> > -- To unsubscribe, e-mail: <mailto:taglibs-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:taglibs-user-help@;jakarta.apache.org>
