Closed GoogleCodeExporter closed 9 years ago
"with Konqueror 3.5.2" at the end of the first sentence above should be
ignored. Bad
editing.
Anyone who wants to look into this but does not have Konqueror can download a
Kubuntu
VMWare image from http://isv-image.ubuntu.com/vmware/. It is much smaller than
my
Gentoo VM, is freely available immediately, and has the advantage of being a
stock
build. Since Gentoo is a source-based distro, there's a remote possibility that
Konqueror was built improperly. I'm downloading Kubuntu 7.10 to test that
possibility.
VMWare Player is available from http://www.vmware.com/download/player/.
Original comment by JessePel...@gmail.com
on 17 Jan 2008 at 8:33
OK, I can reproduce the problem using a Kubuntu 7.10 VM from the site listed
above.
The Konqueror web browser must be configured to report the error, however.
Launch
Konqueror, select "Settings" > "Configure Konqueror..." from the menu, click
"Java &
JavaScript" in the left pane, click the "JavaScript" tab in the right pane,
check
"Report errors" (and "Enable debugger" if you want), and then click "OK." Load
the
test case and the error should be reported.
It's possible (probable?) that the problem is a bug in KHTML. If so, it can be
reported at bugs.kde.org, with product = "konqueror" and component = "khtml
ecma" (I
think). There's a bug stating that extjs doesn't work with Konqueror, which
could
conceivably be related; see http://bugs.kde.org/show_bug.cgi?id=144369.
I'll shut up now, unless I can provide more specifics about what's failing.
Original comment by JessePel...@gmail.com
on 24 Jan 2008 at 3:01
I was wrong. I cannot reproduce this problem with the Kubuntu 7.10 VM, which
includes KDE 3.5.8. I wasn't paying close enough attention to the error I was
getting and when I was getting it. The test case for issue 75 fails the same
way in
Konqueror 3.5.8 that it does with other browsers, as it should. The error
originally
reported in this issue does not occur with this version of Konqueror.
As far as I'm concerned, this issue can be closed as WontFix (or, at a minimum,
marked low priority). I don't think it makes a lot of sense to try to chase
down and
work around a bug in a little-used browser when it was apparently fixed some
time
ago. I suspect that Konqueror users are more likely to stay current than, say,
IE users.
Original comment by JessePel...@gmail.com
on 24 Jan 2008 at 5:26
Thanks for all the detective work. I'll still look into the bug on my linux
box. If I
can recreate it then I'll try to fix it.
Original comment by dean.edw...@gmail.com
on 24 Jan 2008 at 5:35
Original comment by dean.edw...@gmail.com
on 24 Jan 2008 at 5:35
I couldn't recreate it on my setup. I'm going to mark this as "Won't Fix" on the
basis that it's too trivial. :-)
Original comment by dean.edw...@gmail.com
on 24 Jan 2008 at 6:11
Original issue reported on code.google.com by
JessePel...@gmail.com
on 16 Jan 2008 at 8:29