Tersus: Re: On Browse error

Re: On Browse errorDate: Feb 1, 2009Indeed, it is not resolved.Having looked into this issue again, I find the following:Generally speaking, the problem stems from the fact that Tersus dialogs do not block keyboard events from being handled by the dialog's ancestor.More specifically, here are some scenarios:

If view V, has button B which opens dialog D, which contains no input fields, then pressing [Enter] in D, will cause button B to fire again (in effect opening a second dialog D), but if D contains an input field I, [Enter] will be caught by I.

If view V, has input field I, containing an <On Browse> action which opens dialog D, then regardless of whether D contains input fields or not, pressing [Enter], will fire I/<On Browse>.

We shall try to implement a solution for these scenarios, in one of the coming updates.Regards,DavidSee Also:

To use the full functionality of this web site, JavaScript needs to be turned on.

For best results, use the Firefox browser..

Loading ...