We have a secure website where customers can download their telephone statements instead of getting a paper statement. Our Mac customers have reported that they are unable to use Safari to download their statements. A test has shown that when you click on the button to launch the download, nothing happens. On a PC or using an alternate browser, a new window is launched and the PDF is opened in that browser, or downloaded and the user can then open it using another app.
Is there a test account that can be used to test this bug? If you have a Mac available to test, are there any error messages in the JavaScript Console (from the hidden "Debug" menu)? http://www.macosxhints.com/article.php?story=20030110063041629 Could the new window simply be blocked by the pop-up blocking feature in Safari? http://helpdesk.wisc.edu/page.php?id=3279
Per the email request from ddkilzer@kilzer.net, I had a friend try and he said that there is nothing in the debug. I spoke with the web programmer and he said that the button is a bash script which runs in WebCGI. Also, there is no "test" account of which I'm aware. I realize this will make it more difficult. I will advise any of our Mac customers to try this and also advise them of this bug and see if they are willing to provide their info.(In reply to comment #1) > Is there a test account that can be used to test this bug? > > If you have a Mac available to test, are there any error messages in the > JavaScript Console (from the hidden "Debug" menu)? > > http://www.macosxhints.com/article.php?story=20030110063041629 > > Could the new window simply be blocked by the pop-up blocking feature in > Safari? > > http://helpdesk.wisc.edu/page.php?id=3279 > (In reply to comment #1) > Is there a test account that can be used to test this bug? > > If you have a Mac available to test, are there any error messages in the > JavaScript Console (from the hidden "Debug" menu)? > > http://www.macosxhints.com/article.php?story=20030110063041629 > > Could the new window simply be blocked by the pop-up blocking feature in > Safari? > > http://helpdesk.wisc.edu/page.php?id=3279 > (In reply to comment #1) > Is there a test account that can be used to test this bug? > > If you have a Mac available to test, are there any error messages in the > JavaScript Console (from the hidden "Debug" menu)? > > http://www.macosxhints.com/article.php?story=20030110063041629 > > Could the new window simply be blocked by the pop-up blocking feature in > Safari? > > http://helpdesk.wisc.edu/page.php?id=3279 >
Other information that may be helpful: 1. Taking a network trace (using tcpdump or Ethereal) of a Safari user clicking on the button versus a Firefox user clicking on the button, then comparing them for differences in the HTTP requests. (BE CAREFUL! Such data may include private information like session cookies, so I don't recommend posting it unless it's been scrubbed.) 2. The (full?) HTML source of the page which is causing problems. If it's a client-side issue, this may be all that's needed to fix the problem. (Again, BE CAREFUL! The page could include non-public information (NPI) such as account numbers!) Also note that if the web server sends different content based on the user agent string, it will be important for the page to be saved from Safari rather than Firefox or MSIE. If the same content is returned all the time, I suggest using Firefox to save as "Web Page, Complete", SCRUB THE HTML SOURCE for NPI, then zip up the HTML file and the directory it creates and post in in the bug.
It's almost two years without activity on this bug. Without further informations the bug is INVALID. John, feel free to reopen the bug if you provide more useful informations.