On Saturday at 9:36am, DB=>Don Brown <[EMAIL PROTECTED]> wrote:
DB> Ok, I looked at the 1.2.7 source, and indeed, it doesn't generate an
DB> "id" or"name" if xhtml mode is on. You are correct, the styleId is a
DB> good workaround, especially if you use the commons-validator checked
DB> out fro
Ok, I looked at the 1.2.7 source, and indeed, it doesn't generate an
"id" or"name" if xhtml mode is on. You are correct, the styleId is a
good workaround, especially if you use the commons-validator checked
out from trunk.
Don
On 8/20/05, Morris Jones <[EMAIL PROTECTED]> wrote:
> Don Brown wrote
Don Brown wrote:
> You probably enabled xhtml output rendering, which renders an "id"
> attribute instead. Unfortunately, client-side validation in xhtml is
> currently broken in Struts 1.2.7, so you can either checkout and build
> commons-validator or wait until the next release.
Thanks Don, ye
You probably enabled xhtml output rendering, which renders an "id"
attribute instead. Unfortunately, client-side validation in xhtml is
currently broken in Struts 1.2.7, so you can either checkout and build
commons-validator or wait until the next release.
Don
On 8/19/05, Morris Jones <[EMAIL PR
This is an odd problem I haven't run into before ...
The tags in my HTML are coming out without a name="formName"
attribute.
I haven't yet looked at the source code for the tag to see
what might cause the name attribute to be excluded, but I've triple
checked my struts-config to be sure th
5 matches
Mail list logo