Bug 126853

Summary: Font sizes in internal browser differ from konqueror
Product: [Applications] akregator Reporter: Alastair Mailer <alm_mla>
Component: internal browserAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: christophe, gangleri, geneseto
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:

Description Alastair Mailer 2006-05-06 16:35:42 UTC
Version:            (using KDE KDE 3.5.2)
Installed from:    Gentoo Packages
Compiler:          gcc i686-pc-linux-gnu-3.4.5 Using gentoo emerge packages
OS:                Linux

MediaWiki (the wiki engine that runs on many famous wikis e.g. wikipedia) offers an RSS feed of recent changes to the wiki at http://wiki-address.com/index.php?title=Special:Recentchanges&feed=rss. I'm subscribed to several of these wiki feeds. The article summary shows only the diffs of the changed articles. To edit the wiki page or view the entire page you can follow the "Complete Story" link at the bottom of the article. However, when one does this the fonts on the webpage are about twice the size of the page when normally loaded in konqueror. This bug does not appear with my other feeds (kde-look.org and friends). I guess this could be the media-wiki site code being lazy, but the site works fine in standalone konqueror, only the akgregator plugin has trouble rendering it.

How to reproduce:
1. Find a mediawiki site which offers a recent changes RSS feed.
2. Subscribe to the feed in aKregator.
3. Follow the "Complete Story" link at the bottom of one of the articles in the internal konqueror browser.

Observed behaviour: Standard text size is about two times too large.
Expected behaviour: Site renders the same as is stand alone konqueror.
Comment 1 Gene Seto 2008-11-23 00:29:40 UTC
Tested on r887704 compiled with gcc version 4.3.2 (Gentoo 4.3.2 p1.1). 
This appears to be resolved :)

Hum
Comment 2 Christophe Marin 2009-03-08 22:46:49 UTC
I can't reproduce using trunk. Let's assume this bug is fixed now.