14021 Views Previous 1 2 3 Next 42 Replies Latest reply: Mar 12, 2009 4:06 PM by 4Corners Go to original post
so come on Apple and sort out what you changed that stopped their website working. After all you are the experts
Everyone here is just regular users like yourself. Fear not, we share your frustration.
To send feedback to Apple use Safari menu > Report bugs to Apple...
(or more generally, http://www.apple.com/feedback/macosx.html)
And I thought I was the cynical one. I have to say that, although I am not in anyway technically competent in computer software, logic says that as the problem is affecting only HSBC's site it is their problem in the first instance. All through my working life I have had to deal with people who couldn't sort something and therefore blamed someone else rather than admit their limitations. It's only because Apple users are in the minority they are not bothering because if their site didn't work with Windows Explorer I suspect they would deal with it immediately not suggest to Microsoft users to go to Firefox. I have emailed Apple and wait for their response.
Hmm, I'm not convinced that this can be laid at HSBC's door. Their site (or First Direct's in my case) worked with Safari (and continues to work with Safari) so long as you don't update to 10.5.6. It also works with Firefox. The 10.5.6 has broken HTTPS logons to a number of sites (as one of the other threads on here points out).
I hope that we see an Apple fix soon.
Hi Grand Pa Dave,
Although I haven't been suffering like most posters, I did lose my HSBC connection for 1 day this week,
but the next day it was back. I'm still of the opinion that it may be loosely connected to Leopard as a lot of those who have lost the connection are Leopard users, which neither Klaus1 nor myself are.
I know that's no consolation, and I'll be keeping an eye on this thread for future reference.
So does Safari 3.2.1 for Windows (XP SP3). It works fine.
Can't test First Direct with Safari 3.2.1 for Mac OS X 10.4.11 as my PowerMac G4 cannot boot past the first white screen - waiting for a fix ( and free time).
Guess, it is *Safari 3.2.1 (and 4.0 DP) for Mac + OS X 10.5.6 + First Direct (and evidently, HSBC)*.
Use your 'Report bugs to Apple...' facilities and keep sending question to FD about the timescale, folks!
Over one month on now. HSBC's public site message indicates it's a problem they are responsible for and working on, whatever has been written in private e-mails, and Apple has not commented, indicating again that HSBC is at fault.
I have just written to customer service letting them know I am thinking of closing all accounts with them.
I now have a reply from HSBC "IN WRITING" and they say that the problem is with Apple who have now produced a fix but will not say when it will be released although they suspect we will have to wait until Apples quarterly update due on or about the 15th March. As Apple have not replied to any attempts to get this confirmed I can only assume that it is probably correct. Come the 15th March we will finally know who was to blame - so Apple, as Julius Caesar is supposed to have said "beware the Ides of March"!!!
I have to admit that I haven't even ventured tghat far, so bravo for your efforts.
I seems to me that HSBC aren't willing to admit that it's their fault for not using industry standard protocols, but Apple should shoulder some of the responsibility here for not making sure that Safari and Leopard work together.
I'm still OK with Safari and Tiger, so I'm deign to take up with Leopard (or Snow Leopard, for that matter when it arrives) which means that Apple won't be selling me any 'new stuff' in the near future.
As for Julius Caesar: I believe it was actually William Shakespeare who wrote the words, but very eloquently put all the same.
I am having the same issues with a small local bank in South Florida. Ever since I updated I have to basically login to my online bank account twice. It is not only online banking. I am experiencing the same issues with my photo sharing site on smugmug.com. Basically I have to refresh the page twice in order for it to display correctly. Definitely an error on Apples end hope they get it fixed soon....but its not a life or death thing for me.