Currently, I am in the process of developing a user interface within a GWT application for managing Recurly accounts. This setup eliminates traditional browser navigation when moving between "pages" within the app, allowing the client DOM state to be retained in memory until the browser is refreshed by the user.
Essentially, even after leaving the billing information "page," the input elements persist in memory but are hidden from view on the user interface.
However, there seems to be a glitch with the fields provided by "Recurly.js." These fields appear to be optimized for use in a standard framework where form submission leads to a page redirection, making them less compatible with our setup.
Although these fields function flawlessly during the initial submission of updated billing data, they become unresponsive if the user revisits the screen multiple times without refreshing the browser.
I have attempted various solutions such as wiping the inner HTML of the containing recurly div elements and triggering configure() again, but the issue persists. Furthermore, not calling configure() after the first instance causes the inputs to remain unresponsive upon subsequent visits.
Is there a method to instruct Recurly.js to reset itself so that it can redraw the provided fields? Alternatively, is it possible (and preferable) to configure Recurly to utilize custom "input" fields for number, date, month, and CVV instead of the default div-based rendering by Recurly.js?
Your assistance would be greatly appreciated.
Edit:
Upon further inspection, I have found that Recurly.js sets the visibility of their billing inputs to "visibility:hidden" once the form has been accessed following instantiation. If redrawing the inputs is not an option, then I must find a way to prevent this behavior from occurring...