Hi Dave,
Thanks for the quick response. Sorry for the incorrect comparison.
I'm porting a Struts 1 app to Struts 2, so I've got both frameworks on
my mind.
Ok, so the "disabled" attribute on the s:form tag doesn't act the
same as S1. That's cool. Seems like the "disabled" attribute on
s:reset and sx:submit don't work though. I tried
<s:reset value="Reset" class="button" disabled="true"/>
and this renders a working reset button. Also, this
<sx:submit value="Submit" cssClass="button" id="submit"
disabled="true"/>
renders a working submit button. That said "disabled" on an s:submit
correctly renders an inoperable submit button. Any ideas what might be
going on here? Thanks,
Russ
Dave Newton wrote:
Russell Neufeld wrote:
I set disabled="true" in an s:form tag, expecting the resulting form
to be disabled (greyed out, unable to submit by clicking, etc...)
however that appears not be working. I checked the HTML that Struts 2
produced and the "disabled" attribute doesn't show up. I'm using Struts
2.1.6. Any ideas? Is this a known issue? Worked fine in Struts 1.
Functionality comparisons between S1 and S2 are meaningless; they're
completely different frameworks.
According to [1] the form element doesn't have a "disabled" attribute.
In S2 the custom tags all(-ish) inherit from a base class that defines a
list of supported attributes--this doesn't, however, necessarily imply
that the underlying HTML element supports it.
FWIW, a quick sanity-check in FF3 shows no difference if I set a
"disabled" attribute on a form element.
Dave
[1] http://www.w3.org/TR/html401/interact/forms.html#h-17.3
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
