On Monday 02 January 2012 12:19:45 Martin Koller wrote: > > > The details (regressions) I found in the last 3 days: > > > https://bugs.kde.org/show_bug.cgi?id=290375 > > > https://bugs.kde.org/show_bug.cgi?id=290373 > > > https://bugs.kde.org/show_bug.cgi?id=290371 > > > > All KHTML bugs, none of which looks like a release blocker. > > That depends on the defintion of "what is a release blocker". I understood > your comments above, so I can understand that these issues are not "fatal" > in the way that KDE is completely unusable, crashes always, etc. > > > > https://bugs.kde.org/show_bug.cgi?id=290274 (very serious!) > > > > I don't know if the KHTML team actually has the resources to fix these > > bugs, but given that most people use the WebKit part anyway, I wouldn't > > block a release. > > The problem here is: kmail (probably knotes, others) are using khtml only - > at least I know of no way to switch to WebKit in these apps. > And I think it IS very serious if you suddenly can no longer read your mails > correctly (and I'm not talking about HTML mails, since kmail internally > uses khtml to render plaintext mails as well). I attach 2 random > screenshots from kmail here to see what I mean.
Just to clarify this: KMail2 does use QtWebKit exclusively. regards Volker
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
