One twist in my case was, the Chase webapp gave me an error page on about page 5 of the wizard interface, where you upload your payroll documentation. The webapp had no state persisted -- any error and you have to start the whole 25-minute process again. I started again at the beginning, but it errored again at the same spot.
Behind the error message I could make out the text of what appeared to be the ordinary final page of the form. The the error pane was a translucent overlay over the functioning form. I opened Chrome debugger, identified the element, and set its style to "display: none". Et voila: the glorious final page of the form, where I was able to tick off several attestations and press "Submit". About 10 hours later, I received the "application received" message.
You're Chase Bank. You have about 3 days to assemble a webapp that will accept bazillions of hits. You won't have any time to shake it down. Why in the name of Salmon P. Chase do you build a javascript-laden behemoth with a slick wizard interface with page transitions, that has a session timer but no persisted saved state (of any use to the user), using XHR file uploads, the combination of all that hot code bound to fail on any browser but Chrome (it failed to get to page 1 using Firefox)?
They could have built a plain old HTML single-page form with a POST action that would upload all the attachments. It could even have had wonderful CSS to support the branding they feel they must have. The whole thing could have run on Apache hosts with a CGI handler. Seriously.
Behind the error message I could make out the text of what appeared to be the ordinary final page of the form. The the error pane was a translucent overlay over the functioning form. I opened Chrome debugger, identified the element, and set its style to "display: none". Et voila: the glorious final page of the form, where I was able to tick off several attestations and press "Submit". About 10 hours later, I received the "application received" message.
You're Chase Bank. You have about 3 days to assemble a webapp that will accept bazillions of hits. You won't have any time to shake it down. Why in the name of Salmon P. Chase do you build a javascript-laden behemoth with a slick wizard interface with page transitions, that has a session timer but no persisted saved state (of any use to the user), using XHR file uploads, the combination of all that hot code bound to fail on any browser but Chrome (it failed to get to page 1 using Firefox)?
They could have built a plain old HTML single-page form with a POST action that would upload all the attachments. It could even have had wonderful CSS to support the branding they feel they must have. The whole thing could have run on Apache hosts with a CGI handler. Seriously.