List,
I am experiencing a problem where the JavaScript execution context in
Firefox and Safari is lost after returning a Resolution from an error
handler.
Items like the ³console,² e.g., console.log(³someMessage²), fail with
³console is undefined². More importantly, my client form validation
initially fails to execute until the form is submitted a second time with
errors.
Now, ³console² is a value defined globally in the JavaScript engine and
automatically exposed in Safari and Firefox. If I reload the page, the
context returns.
Specifically, my initial page load is to a view (³Inbound.action²) with some
blank fields. These fields are bound to and submit to an action
(³DirectList.action²) which evaluates the form and returns on errors by
using:
res = getContext().getSourcePageResolution();
The old view is in the context of the DirectList.action.
It appears that the browser will not execute the Javascript context until
refresh. This might be a browser problem, however, it appears to be
something about the Stripes resolution on the error round trip.
Any thoughts? The scripts all work on the initial view, but fail on the next
view, so I¹ve generally eliminated a problem with the script, and this
console issue is *very suspect*.
Much thanks,
Tim
Barclays www.barclaycardus.com
This e-mail and any files transmitted with it may contain confidential and/or
proprietary information. It is intended solely for the use of the individual or
entity who is the intended recipient. Unauthorized use of this information is
prohibited. If you have received this in error, please contact the sender by
replying to this message and delete this material from any system it may be on.
------------------------------------------------------------------------------
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
