Massive Konqueror Regression

P Botha bothapn at lantic.net
Sun Aug 14 16:07:38 CEST 2005


On Sunday 14 August 2005 15:55, Rudo Thomas wrote:
> > the source to the pages themselves usually isn't the best thing for the
> > developers anyways. what is best is a reduced, simplified bit of example
> > HTML/Javascript/CSS/whatever that shows the problem succinctly and
> > directly. this usually means save the page locally and then removing all
> > the bits that aren't related to the problem until you have a generic test
> > case. this sometimes takes a while because it requires hunting for what
> > it triggering the problem.
> >
> > this is very valuable to the developers because it saves them from doing
> > this and allows them to quickly see what the problem is exactly and then
> > go about fixing it quickly.
>
> I am sorry to say that my exprerience has been different.
>
> http://bugs.kde.org/show_bug.cgi?id=74569
>
> There is a simple test case, as well as a full back-trace. The bug is
> still present in the latest version of konqueror, though :-(
>
> This is not to say that providing simple test cases is pointless, it is
> just the lone case when I actually submitted this kind of bug report.
>
> Bye.
>
> Rudo.
> _______________________________________________
> kde-quality mailing list
> kde-quality at kde.org
> https://mail.kde.org/mailman/listinfo/kde-quality
Un-reproducible in Konqueror 3.4.2 Suse 9.3 x64.

Pieter


More information about the kde-quality mailing list