Bug 106018 - [site-issue] www.tomshardware.com does not display correctly in aKregator
Summary: [site-issue] www.tomshardware.com does not display correctly in aKregator
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-20 14:00 UTC by cjb
Modified: 2006-12-11 23:42 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description cjb 2005-05-20 14:00:51 UTC 
Version:           unknown (using KDE 3.4.0 Level "b" , SUSE 9.3)
Compiler:          gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)
OS:                Linux (i686) release 2.6.11.4-20a-default

Articles coming from the RSS feed of Tom's Hardware (www.tomshardware.com) will not render correctly in Kontact/akregator window. These articles will display correctly if an external browser is used.
Comment 1 Stephan Binner 2005-05-22 23:05:39 UTC 
"External browser" can also be Konqueror?
Comment 2 Frank Osterfeld 2005-05-22 23:25:41 UTC 
On my box, rendering brokeness depends on the width of the browser widgets:
Using a small width the layout is broken, making it wider fixes it. Whether Akregator or Konqueror, it makes no difference.
But: In Konqueror, your normally use (nearly) the full screen width for the KHTML widget, in Akregator maybe about 2/3. So the view is wider in Konq and thus the pages are rendered correctly there but not in Akregator.
Comment 3 cjb 2005-05-23 01:27:13 UTC 
Could this problem be avoided if Konqueror/Akregator provided a "Fit to width" option like the Opera (version 8.0) browser?
Comment 4 Eckhart Wörner 2005-05-29 10:07:38 UTC 
This is no Akregator specific problem but a KHTML problem.
Comment 5 Philip Rodrigues 2006-09-02 22:21:43 UTC 
Is there a testcase where we can see the problem to verify whether it still exists?
Comment 6 Philip Rodrigues 2006-12-11 23:42:14 UTC 
Feedback timeout, but please reopen this report if the problem still occurs in KDE 3.5