Bug 13449 - JavaScript error on web.ebscohost.com (ReferenceError: Can't find variable: __doPostBack)
Summary: JavaScript error on web.ebscohost.com (ReferenceError: Can't find variable: _...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 523.x (Safari 3)
Hardware: Mac (Intel) OS X 10.4
: P2 Normal
Assignee: Nobody
URL: http://web.ebscohost.com
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-22 11:00 PDT by Steve Moxey
Modified: 2022-07-06 16:28 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Moxey 2007-04-22 11:00:11 PDT 
Links from EBSCO, one of the main academic research sites have stopped working, I think this was after the recent security update to Mac OS X. There are errors when links are clicked in the javascript console for WebKit:

ReferenceError: Can't find variable: __doPostBack
Comment 1 David Kilzer (:ddkilzer) 2007-04-23 07:43:41 PDT 
Thanks for the bug report, Steve!  When I try the URL above (http://web.ebscohost.com), I just get a 404 error page.  Is an account required to test/reproduce the bug?

Have you tried a WebKit nightly to see if the bug still exists?  http://nightly.webkit.org/  Simply download the DMG, mount it, and double-click the gold Safari icon try try it out.
Comment 2 David Kilzer (:ddkilzer) 2007-04-24 14:07:44 PDT 
(In reply to comment #1)
> Is an account required to test/reproduce the bug?

Yes.

> Have you tried a WebKit nightly to see if the bug still exists? 

The nightly WebKit Steve tried produced the same error.  Marking as confirmed per Steve's testing.

Adding "NeedsRadar" keyword since there may be some sensitive information that is required (an account) to reproduce the bug.
Comment 3 David Kilzer (:ddkilzer) 2009-07-22 11:59:09 PDT 
Steve, does this error still occur on Safari 4.0.2?
Comment 4 Brent Fulgham 2022-07-06 16:28:14 PDT 
The website seems to return an error message. Not sure what action we can take here.