Bug 134874 - javascript errors with wwe.com
Summary: javascript errors with wwe.com
Status: RESOLVED DUPLICATE of bug 160466
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-29 23:08 UTC by Jeffrey Parke
Modified: 2008-10-03 01:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
proof of javascript error in kubuntu 6.06.1 (254.42 KB, image/png)
2006-09-30 18:48 UTC, Jeffrey Parke
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeffrey Parke 2006-09-29 23:08:25 UTC
Version:           3.5.4 (using KDE 3.5.4, Kubuntu Package 4:3.5.4-0ubuntu2~dapper1 )
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-27-386

When I go the WWE home page (www.wwe.com), there are some javascript errors that come up. 

Error: http://www.wwe.com/: ReferenceError: Can't find variable: OAS_RICH
Error: http://www.wwe.com/: ReferenceError: Can't find variable: OAS_RICH
Error: http://www.wwe.com/: ReferenceError: Can't find variable: OAS_RICH

there are similar javascript errors throughout the site.

note: this may be a html problem.
Comment 1 Marc Collin 2006-09-30 06:06:54 UTC
don't have any javascript problem with konqueror 3.5.4 (suse)
Comment 2 Jeffrey Parke 2006-09-30 18:48:26 UTC
Created attachment 17971 [details]
proof of javascript error in kubuntu 6.06.1

This is proof of the javascript error. I am using Kubuntu 6.06.1
Comment 3 FiNeX 2008-06-01 19:18:06 UTC
Using Konqueror from KDE4 (trunk) I've different JS Errors:

http://www.wwe.com/js/s_code.v2.js: ReferenceError: Can't find variable: s_d
http://www.wwe.com/: TypeError: Undefined value

Instead Konqueror 3.5.9 doesn't show this errors.
Comment 4 Maksim Orlovich 2008-10-03 01:50:47 UTC
Just fixed this..

*** This bug has been marked as a duplicate of bug 160466 ***