Bug 56103 - www.bluesnews.com renders incorrectly before settings dialog
Summary: www.bluesnews.com renders incorrectly before settings dialog
Status: RESOLVED DUPLICATE of bug 54956
Alias: None
Product: konqueror
Classification: Applications
Component: khtml renderer (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR major
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 55692 55899 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-03-18 20:26 UTC by danarmak
Modified: 2003-10-25 19:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description danarmak 2003-03-18 20:26:46 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc 3.2.2 
OS:          Linux

In both kde 3.1.1 and cvs head (as of March 17), www.bluesnews.com renders incorrectly in that the links are blue text on blue backgruond and so almost unreadable.
However if I access the configure dialog, and immedeatly press OK (changing no settings), the page renders correctly (yellow links on blue background). This points to it being a bug in konqeuror, as opposed to a badly written page or something else.

Ref: http://bugs.gentoo.org/show_bug.cgi?id=17382 (no extra info there atm except that the user who reported it isn't me, so we've both reproduced this under different configs and kde versions).
Comment 1 Thiago Macieira 2003-03-19 00:16:23 UTC
Confirming this behaviour. 
 
The page has no stylesheets or similar things. It contains: 
 
<BODY text="#ffffff" vLink="#c0c0c0" link="#ffff84" bgColor="#072245" 
leftMargin="8" topMargin="8"> 
 
i.e., the link colours should be yellowish, not blue. 
 
The HTML validator at w3c.org shows some bizarre results for that page, like 
</HEAD> closing an unopened tag, which is opened. 
Comment 2 Kai Lahmann 2003-06-14 20:36:24 UTC
*** Bug 55692 has been marked as a duplicate of this bug. ***
Comment 3 Kai Lahmann 2003-06-14 21:07:13 UTC
*** Bug 55899 has been marked as a duplicate of this bug. ***
Comment 4 Karl Vogel 2003-10-19 14:51:46 UTC
Same as reported in: Bug 54956: Wrong rendering of links
Comment 5 Stephan Binner 2003-10-23 18:44:05 UTC
Enters 100% CPU load when loading:

#0  0x400ccd2d in int const& kMax<int>(int const&, int const&) () from /opt/kde-cvs/lib/libkdeinit_konqueror.so
#1  0x4233edbd in khtml::RenderLayer::height() const () from /opt/kde-cvs/lib/libkhtml.so.4
#2  0x4235e902 in khtml::RenderCanvas::docHeight() const () from /opt/kde-cvs/lib/libkhtml.so.4
#3  0x4235d5c6 in khtml::RenderCanvas::layout() () from /opt/kde-cvs/lib/libkhtml.so.4
#4  0x422762a6 in KHTMLView::layout() () from /opt/kde-cvs/lib/libkhtml.so.4
#5  0x4227ec74 in KHTMLView::timerEvent(QTimerEvent*) () from /opt/kde-cvs/lib/libkhtml.so.4
#6  0x40d4e63e in QObject::event(QEvent*) () from /usr/src/qt-copy-3.2/lib/libqt-mt.so.3
#7  0x40d82e12 in QWidget::event(QEvent*) () from /usr/src/qt-copy-3.2/lib/libqt-mt.so.3
#8  0x40cf5451 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/src/qt-copy-3.2/lib/libqt-mt.so.3
#9  0x40cf4a37 in QApplication::notify(QObject*, QEvent*) () from /usr/src/qt-copy-3.2/lib/libqt-mt.so.3
#10 0x4088651b in KApplication::notify(QObject*, QEvent*) () from /opt/kde-cvs/lib/libkdecore.so.4
#11 0x40ce4f9b in QEventLoop::activateTimers() () from /usr/src/qt-copy-3.2/lib/libqt-mt.so.3
#12 0x40ca45d4 in QEventLoop::processEvents(unsigned) () from /usr/src/qt-copy-3.2/lib/libqt-mt.so.3
#13 0x40d07f9c in QEventLoop::enterLoop() () from /usr/src/qt-copy-3.2/lib/libqt-mt.so.3
#14 0x40d07e94 in QEventLoop::exec() () from /usr/src/qt-copy-3.2/lib/libqt-mt.so.3
#15 0x40cf56e0 in QApplication::exec() () from /usr/src/qt-copy-3.2/lib/libqt-mt.so.3
#16 0x40064f0d in kdemain () from /opt/kde-cvs/lib/libkdeinit_konqueror.so
#17 0x08048677 in main (argc=1, argv=0xbffff334) at konqueror.la.cc:2
#18 0x415578ae in __libc_start_main () from /lib/libc.so.6
Comment 6 Stephan Kulow 2003-10-25 19:42:26 UTC
works fine here. But the #5 I saw with other test cases

*** This bug has been marked as a duplicate of 54956 ***