Hi, pardon me but it seems almost nonsense to me: would users fill forms in a language they can't even understand? For instance: I'm italian, I speak Italian and English but I'm required to fill a form in Swahili. I would understand validation messages for sure (they would come from my UA) but I couldn't understand why they don't satisfy their constraints, what I'm supposed to fill and when I should submit the form.
A clarification is needed. Il giorno 10/nov/2009, alle ore 23.37, Scott González ha scritto: > Wouldn't the UA be written for a specific language that would be independent > of the language the page's content is written in? For example, a user in > Spain would be using a UA with a Spanish locale (the UA's menus, dialogs, > button labels, etc. would all be in Spanish). If that user were to visit a > page written in French wouldn't the content generated by the UA still be in > Spanish? So an alert would contain a message in French, but a button in > Spanish. I would expect the same thing to happen with validation messages. > > As for the suggestion of the validation message just being a constant, you > can just check the validity state if you want to provide custom messages. > > > On Tue, Nov 10, 2009 at 4:23 PM, Michelangelo De Simone <[email protected]> > wrote: > Hi, > > I've been dealing with the validationMessage implementation in WebKit. As > some of WebKit member pointed out it's quite unusual for an attribute to > "return a suitably *localized message* that the user agent would show the > user". > > Couldn't such behavior be potentially heterogeneous among UAs and > localizations? > > What is the rationale about this choice? A simpler behavior with a > predetermined list of return values (eg: i.validationMessage == VALUEMISSING) > could be much more efficient for authors and implementors to deal with, IMHO. > > Thank you for your feedbacks. > -- > Bye, Michelangelo > > > > -- Bye, Michelangelo
