RESOLVED INVALID 13702
JavaScript error on Get A Mac TV Ads page
https://bugs.webkit.org/show_bug.cgi?id=13702
Summary JavaScript error on Get A Mac TV Ads page
David Kilzer (:ddkilzer)
Reported 2007-05-12 17:55:49 PDT
* SUMMARY JavaScript error using Get A Mac web page. See Steps to Reproduce for details. Not sure if this is a web site issue or a browser issue, but Firefox 2.0.0.3 has a related problem (complains about needing QuickTime 7 when it's already installed, along with a JavaScript error). * STEPS TO REPRODUCE 1. Open Safari/WebKit. 2. Go to URL: http://www.apple.com/getamac/ads/ 3. Scroll down, and click the right arrow (next to the row of videos) two times. (Don't double-click, click once, wait for the videos to scroll, then click again. You may do this while the default movie on the page is playing.) 4. Click on one of the videos in the row to play it. * EXPECTED RESULTS The video that was clicked on should start playing. * ACTUAL RESULTS A JavaScript error occurs. * REGRESSION Actual results seen with a local debug build of WebKit r21427 with Safari 2.0.4 (419.3) on Mac OS X 10.4.9 (8P135). Have not tested shipping Safari/WebKit alone. * NOTES See also Bug 13653 for a different issue on the same page.
Attachments
David Kilzer (:ddkilzer)
Comment 1 2007-05-12 17:56:16 PDT
Here's the error from the JavaScript console: Null value http://wdirect.apple.com/main/js/lib.js Line: 61
David Kilzer (:ddkilzer)
Comment 2 2007-05-12 18:17:21 PDT
(In reply to comment #0) > * REGRESSION > Actual results seen with a local debug build of WebKit r21427 with Safari 2.0.4 > (419.3) on Mac OS X 10.4.9 (8P135). Have not tested shipping Safari/WebKit > alone. This occurs in shipping Safari 2.0.4 (419.3) on Mac OS X 10.4.9 (8P135) as well. Opera 9.10 exhibits the same behavior as Firefox 2.0.0.3.
Alexey Proskuryakov
Comment 3 2007-05-20 00:34:44 PDT
Per comment 2, this doesn't seem to be a WebKit issue, does it?
David Kilzer (:ddkilzer)
Comment 4 2007-05-20 06:54:53 PDT
(In reply to comment #3) > Per comment 2, this doesn't seem to be a WebKit issue, does it? Nope.
Note You need to log in before you can comment on or make changes to this bug.