Safari test case (Javascript and Links)

I created a test case for Safari, that shows it failing to launch a URL when clicked. The issue is caused by some Javascript that is valid in IE and Mozilla. View the source of the page to see the offending javascript code.

I just hope that Apple sees and fixes this issue now that I have tracked it down to just one small javascript issue.

(Sorry Dave (site defunct) for emailing you directly regarding this issue!!!)

Update: AHHH stupid trackback, MT/Kung-Long posted my trackback to Surf’n Safari 3 times! I’m having no luck here today folks sigh

Update: Some people posted that Mozilla was giving errors with JavaScript.

Error: document.getElementById(“department_popup”) has no properties
Error: oStatic has no properties

I removed the offending lines of code, which really had impact on the test case.

← Back

5 comments

Archived from the original post. Comments are closed.

  1. bcat

    Well, it does work with Konqueror 3.1.2. However, the test case produces errors in the Firebird JavaScript console.

    One of these every time I move the mouse:
    Error: oStatic has no properties
    Source File: http://ddll.sdf1.net/test/SafariTestCase.html
    Line: 106

    This one when the test link is clicked:
    Error: document.getElementById("department_popup") has no properties
    Source File: http://ddll.sdf1.net/test/SafariTestCase.html
    Line: 68

    Maybe fixing these will make it work in Safari?

  2. bcat

    Your test case works in Konqueror 3.1.2. But running it under Mozilla Firebird produces these JavaScript errors:

    This one every time I move the mouse:
    Error: oStatic has no properties
    Source File: http://ddll.sdf1.net/test/SafariTestCase.html
    Line: 106

    This one when the link is clicked:
    Error: document.getElementById("department_popup") has no properties
    Source File: http://ddll.sdf1.net/test/SafariTestCase.html
    Line: 68

    Maybe fixing these makes it work under Safari?

  3. Ray Slakinski

    I'll have to fix that, I'll post back here if that fixes the issue.

  4. Ray Slakinski

    As stated in the above update, I fixed the javascript error, but this does not fix the issue in Safari

  5. Ray Slakinski

    Paxil, I'm a little confused by your comment, can you expand on your viewpoint?

    Thanks