doPostBack Failure With Safari 5.1.4

Question

Level 1

112 points

doPostBack Failure With Safari 5.1.4

Our bank's website uses a _doPostBack JavaScript "link" to open a clicked account's transaction page, but Safari 5.1.4 seems to kill this functionality. Clicking the link does nothing -- it never registers at all. Here's the link format:

javascript:__doPostBack('ctl00$PageContent$ctl00$_acctsBase$_depositsTab$_deposi tsGrid$ctl03$_designator','')

The WebKit Nightly Builds work perfectly. I have reported the issue, as well -- just wondering if anyone else has run into this and found a workaround. And yes, JS is fully enabled and working.

Posted on Mar 20, 2012 7:09 AM

Reply

Answer 1

Mar 21, 2012 3:49 PM in response to Maury Mccown

I am experiencing the same issue with may bank's online website and Safari 5.1.4. _doPostback... fails. Chrome and Firefox both work.

I did ensure that Safari is opening in 64-bit mode as was mentioned on other threads.

Reply

Answer 2

Mar 22, 2012 8:05 AM in response to billvencil

I guess this is what I am seeing as well. When I try and login to my Mellon account it fails on the second screen. I did not know what was going on but it sounds like this. I have reported to Apple as well. I tried an old machine with Safari 5.0.4 and it works fine.

Reply

Answer 3

Mar 24, 2012 1:02 PM in response to Maury Mccown

I am currently using safari 5.1.4 and also getting the _doPostback... fails when online banking. It is very frustrating. I am keep to find a fix.

Reply

Answer 4

Mar 26, 2012 1:56 PM in response to Maury Mccown

I have the same problem with the City of Berkeley Building Permit Status website. The link fails under Safari 5.1.4 and also fails under Firefox 11.0. It works on an old Power PC Mac running Safari 4.1.3.

So if you have an old Mac, I guess that's a workaround.

Reply

Answer 5

Mar 26, 2012 2:28 PM in response to Maury Mccown

More info: just tried it using Safari 5.1.4 on an iMac 6,1 and on an iMac 8,1 and it worked OK on both of them. Does not work on my MacBookPro.

Reply

Answer 6

Maury Mccown Author

Level 1

112 points

Mar 27, 2012 11:45 AM in response to rm architect

Safari 5.1.5 exhibits the same behavior. Latest WebKit still works fine, though.

Reply

Answer 7

Maury Mccown Author

Level 1

112 points

Mar 27, 2012 11:45 AM in response to rm architect

Safari 5.1.5 exhibits the same behavior. Latest WebKit still works fine, though.

Reply

Answer 8

b noir

Level 9

72,336 points

Mar 27, 2012 6:04 PM in response to Maury Mccown

Just a thought by way of possible workarounds ... are the affected customers able to get past the trouble if they log on using a different user agent?

To get access to the User agents via the Develop Menu, go into your Safari advanced preferences and select "Show develop menu in menu bar":

Reply

Answer 9

Mar 28, 2012 4:01 AM in response to Maury Mccown

Changing the user agent to Safari for iPad worked, I tried Internet Exporer 8.0 and that did not work. What is the consequence of using an alterante user agent?

Reply

Answer 10

Maury Mccown Author

Level 1

112 points

Mar 28, 2012 6:14 AM in response to Maury Mccown

This is so odd...

- Suddenly, my 5.1.3 install on my Mac Pro quit doing the doPostBack. TOTALLY random.

- I went ahead and upgraded to 5.1.5, same issue.

- I changed the User Agent to *anything* except Safari and it worked.

- I changed the User Agent back to Default/Automatic, and it worked. ???

- I Quit and Closed All Windows, leaving the UA Default -- and it still worked.

At this point, the issue is resolved somehow by merely changing the UA. I don't know if there's a cookie or something stored and the UA really isn't being released... ???

Reply

Answer 11

Mar 28, 2012 6:32 AM in response to Maury Mccown

No matter what I do in Safari, user agent canges or anyting it still does not work with my Mellon account log in. Google Chrome works fine as does Firefox. I have sent Apple the failed pages many times but no response yet. When I tried Safari 5.0.4 on an old machine it wokred just fine so Apple has broken something.

Reply

Answer 12

Mar 28, 2012 7:35 AM in response to Maury Mccown

I just tried Webkit and it works fine. So what is wrong wiht Safari and Apple?

Reply