I agree it's a big problem, and fixing it should be a priority. I don't think we can hold up 1.0.1 for it, since the fix won't be quick.
-- Adam On 6/12/07, Luka Surija <[EMAIL PROTECTED]> wrote:
http://issues.apache.org/jira/browse/TRINIDAD-2 Broken client decimal number validator is still not solved. Matthias has worked on this problem, but in my case the problem still remains. I think this is a big problem for everyone who hasn't default decimal separator and thousand separator. Luka Adam Winer wrote: > Does anyone have high-priority issues they'd like resolved > for 1.0.1? > > I'd very much like to switch the default validation mechanism > from ALERT to INLINE, as I think that's the "killer feature" > for this release. We also need some real release notes, > seein' as we're a grown-up project and all. :) I'll give > that a whirl. > > In addition, I'm thinking we should resolve at least: > > http://issues.apache.org/jira/browse/TRINIDAD-50 > ClassCastException in ExternalContextUtils > > ... but that we should postpone: > > http://issues.apache.org/jira/browse/TRINIDAD-35 > Dialog Framework to support 'iframe/lightweight' dialogs > http://issues.apache.org/jira/browse/TRINIDAD-46 > Switch from IFRAMEs to XMLHttpRequest for non-fileupload requests > http://issues.apache.org/jira/browse/TRINIDAD-51 > Support manually adding SetActionListener > > And @Jeanne, isn't > http://issues.apache.org/jira/browse/TRINIDAD-49 > resolved? > > -- Adam >
