Version: (using KDE KDE 3.1.2) Installed from: Mandrake RPMs OS: Linux When accessing the Chiq-Chaq Wiki "Recent_Changes" page, an error is generated due to JavaScript incompatibility. Chiq Chaq is compatible with either MSIE 5 and above or Mozilla 1.2 and above, and it works fine in these browsers. To see it in action, check: http://www.beofen-tv.co.il/cgi-bin/chiq.pl?group=eng&title=Recent_Changes
I only see an "page procession error", which doesn't say me, what's wrong...
Subject: Re: Chiq-Chaq's "Recent_Changes" page generates an error. On Sun, 15 Jun 2003, Kai Lahmann wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=59803 > > > > > ------- Additional Comments From kl@3dots.de 2003-06-15 13:12 ------- > I only see an "page procession error", which doesn't say me, what's wrong... > There's the Error in the Error text area. Also, try viewing the same page with Mozilla and see the difference. Regards, Shlomi Fish ---------------------------------------------------------------------- Shlomi Fish shlomif@vipe.technion.ac.il Home Page: http://t2.technion.ac.il/~shlomif/ An apple a day will keep a doctor away. Two apples a day will keep two doctors away. Falk Fish
The Error field is empty for me. What do you see?
Subject: Re: Chiq-Chaq's "Recent_Changes" page generates an error. On Sun, 15 Jun 2003, Thiago Macieira wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=59803 > > > > > ------- Additional Comments From thiagom@mail.com 2003-06-15 14:33 ------- > The Error field is empty for me. What do you see? > I see this: <<< Error in function "ccLoader('/cgi-bin/chiq.pl?new=3&format=xml&&group=eng') at point 12": TypeError: Expression is no object. Cannot be called. #0#0# Expression is no object. Cannot be called. Error in function "ccLoader('/afics/recent-pre.xsl') at point 12": TypeError: Expression is no object. Cannot be called. #0#0# Expression is no object. Cannot be called. Error in function "ccLoader('/afics/recent-post.xsl') at point 12": TypeError: Expression is no object. Cannot be called. #0#0# Expression is no object. Cannot be called. >>> Regards, Shlomi Fish ---------------------------------------------------------------------- Shlomi Fish shlomif@vipe.technion.ac.il Home Page: http://t2.technion.ac.il/~shlomif/ An apple a day will keep a doctor away. Two apples a day will keep two doctors away. Falk Fish
I don't see any errors either, just the red title
I see the code (assuming Mozilla) tries to execute window.getSelection(). An extension we could possibly implement as well.
I can confirm that this page is still broken with Konqi 3.5.4, and works with FF 1.5. I note that if I tell Konqi to ID as IE 5.01 on win2k, I get a different result that *almost* works. Regards, Mark A. Taff
Can also confirm
*** Bug 132048 has been marked as a duplicate of this bug. ***
This uses XSLTProcessor, and is fully of icky browser-specific code. Still exists in 4.0 r793981
Well, the general case XSLT issue needs to be resolved I guess (or at least hope). But I wouldn't mind Chiq-Chaq breaking in Konqueror, because it's really poorly written and not designed for compatibility and portability in mind. Its server-side Perl code is very bad and does not make use of many common Perl best practices and safety measures (e.g: "use strict", "use warnings", to say nothing of tainting). Arguably the same thing can be said of many Wiki engines, but as opposed to most other popular wiki engines, Chiq-Chaq's semantics are pretty bad too. And Chiq-Chaq was not very popular the last time I checked. I'm no longer using Chiq-Chaq and wouldn't recommend it. It has some unique features, but I think you can find a suitable alternative. I suggest closing this bug or at least filing a different bug instead, unless someone wishes to build a workaround for its JS code, which I don't care to debug since I'm no longer using Chiq-Chaq.
@konqueror-devs: what about this bug? Should it be considered as closed or is still valid on KDE 4 ???????
Closing as outdated. Feel free to reopen a new report if you can reproduce this with Konqueror 4.8.4 or later.