----- Original Message ----- From: "David Graham" <[EMAIL PROTECTED]> Sent: Wednesday, April 13, 2005 2:08 AM
> > > This page http://www.quirksmode.org/index.html?/dom/error.html
--- Niall Pemberton <[EMAIL PROTECTED]> wrote: > ----- Original Message ----- > From: "Joe Germuska" <[EMAIL PROTECTED]> > Sent: Tuesday, April 12, 2005 8:54 PM > >> > demonstrates a more graceful way of alerting users to errors in their > > form than an "alert" window. (In case you don't feel like clicking, > > it uses Javascript and the DOM to add a message and change the CSS > > style of the error fields.) > > > > Can anyone think of a good way to open up the validator javascript so > > that a user could plug in handling like this when desired? Perhaps > > we could define a "handleErrors(obj)" method which would receive an > > array of error objects, and the default implementation would do the > > same thing which currently happens now; then users could simply > > redefine the function if they wanted to do something fancier. > > Thats one of the things I was aiming for in the validator enhancement I > was > working on. Part of the problem though is in letting the handleErrors() > method know where to put a particular fields error message and what css > style to set - or if valid reset.
Maybe give handleErrors() the css id of an element that it can set the innerHTML property on to write the error message?
The question is where to get that id from. The JavaScript validation is generated from whats defined for the form in the validation.xml, with no reference to whats in the jsp/html except for the property name. Without adding additional display attributes there, then I guess the simplest option is to assume an id based on the property name with a standard prefix/suffix.
Well, if you are validating an input element, then you have a handle on something in the DOM. And my point isn't so much to make Struts (or Commons Validator) figure out the best advanced solution as it is that we should leave a route for those who want an advanced solution to implement it. But in any case, the QuirksMode.org page does its tricks relative to the same object which would be used for validation, so I don't think it has to be as complicated as it seems that you (Niall and David) are interpreting it.
Also, simply for backwards compatibility, the first approach has to be to expose extensibility without changing the behavior.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
