Bug 158067 - java script support cause errors in some pages
Summary: java script support cause errors in some pages
Status: RESOLVED DUPLICATE of bug 155493
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-19 22:00 UTC by Khalil Moriello
Modified: 2008-02-21 08:04 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Khalil Moriello 2008-02-19 22:00:21 UTC
Version:            (using KDE 4.0.1)
Installed from:    Debian testing/unstable Packages
OS:                Linux

When I try to load some pages with java and java script on, they aren't shown properly. For example  http://msdn2.microsoft.com/en-us/library/2x7c9kxh(VS.71).aspx and www.fotolog.com/**. Konqueror shows error s in the codification.
If I open these pages with mozilla they'll be shown properly.
Comment 1 Khalil Moriello 2008-02-19 22:02:24 UTC
Sorry I forgot putting the version. I'm using KDE 4.0.1 and konqueror 4.0.1 from debian experimental repositories.
Comment 2 Tommi Tervo 2008-02-20 08:43:31 UTC
Don't sumbit many bugs in one report. msdn bug is dupe of bug #155299.
For me konqueror 4.0.1 and firefox 2.0 renders fotolog.com page similar way. Firefox reports same javascript error that konqueror shows: missing )-mark after argument list. So what's problem?
Comment 3 Khalil Moriello 2008-02-21 05:53:21 UTC
For example in fotolog.com in konqueror the error says: Error: http://si.fotolog.com/i57/js/lib/jquery.fAjax.js: Error de análisis en http://si.fotolog.com/i57/js/lib/jquery.fAjax.js line 34
When you open a fotolog page, for example www.fotolog.com/xxx you can see photos and comments but when you want to see the previous photo, the page loads and it's white without anything.

En iceweasel 2.0.0.11 it doesn't show me anything about problems.
Comment 4 Maksim Orlovich 2008-02-21 06:48:41 UTC
I've seen this parse error before, I think. I am pretty sure this report is a dupe. BTW, IceWeasel not issuing this parse error is actually a standards non-compliance in it (though it seems we're a tad too loose about where we accept function declarations, too, which makes IW's other function declaration "features" less bad). The code itself is obviously not written right, though. Not sure it has anything to do with the problem you're reporting, anyway
Comment 5 Tommi Tervo 2008-02-21 08:04:55 UTC

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