Bug 240465 - rendering bug on many mediawiki sites
Summary: rendering bug on many mediawiki sites
Status: RESOLVED UPSTREAM
Alias: None
Product: kwebkitpart
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: webkit-devel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-02 14:31 UTC by Adrian von Bidder
Modified: 2010-06-02 22:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot of rendering bug (56.37 KB, image/png)
2010-06-02 14:31 UTC, Adrian von Bidder
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian von Bidder 2010-06-02 14:31:33 UTC
Created attachment 47606 [details]
screenshot of rendering bug

Version:           unspecified (using KDE 4.4.3) 
OS:                Linux

This is Debian squeeze + kpart-webkit debian package updated to  svn1129464

Many mediawiki pages show the rendering issue shown in the screenshot (navigation area rendered below content); khtml renders the same pages just fine.  Wikipedia or mediawiki.org itself doesn't have the problem.

Reproducible: Always

Steps to Reproduce:
http://www.debianclusters.org/
Comment 1 Dawit Alemayehu 2010-06-02 19:29:58 UTC
Indeed I can reproduce this bug. However it happens with all QtWebKit based browsers and as such it is an upstream issue. Please open a ticket in QtWebKit bug tracking database. Here is a link that explains how to reports issues against QtWebKit...

https://trac.webkit.org/wiki/QtWebKitBugs
Comment 2 Adrian von Bidder 2010-06-02 20:08:41 UTC
done.
https://bugs.webkit.org/show_bug.cgi?id=40073
Comment 3 Dawit Alemayehu 2010-06-02 22:37:30 UTC
On Wednesday, June 02, 2010 14:08:41 Adrian von Bidder wrote:
> https://bugs.kde.org/show_bug.cgi?id=240465
> 
> 
> 
> 
> 
> --- Comment #2 from Adrian von Bidder <avbidder+kde fortytwo ch> 
> 2010-06-02 20:08:41 --- done.
> https://bugs.webkit.org/show_bug.cgi?id=40073

You should set the "Keyword" field in that report to "Qt" as well...