Bug 155299 - MSDN pages rendered incorrect
Summary: MSDN pages rendered incorrect
Status: RESOLVED UNMAINTAINED
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:
: 136704 158025 185505 185704 194988 218385 231985 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-01-08 21:26 UTC by Edwin Schepers
Modified: 2024-05-06 18:39 UTC (History)
8 users (show)

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 Edwin Schepers 2008-01-08 21:26:04 UTC 
Version:           4.00.80 (KDE 4.0.80 >= 20080104) (using KDE 4.00.80 (KDE 4.0.80 >= 20080104), compiled sources)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.22-5-default

Hi,
For example : http://msdn2.microsoft.com/en-us/library/aa139615.aspx, the frame doesn't show the menu. On pages without the frame, the menu works correctly ( http://msdn2.microsoft.com/en-us/netframework/default.aspx ).

Also, the feedback part doesn't work and is rendered incorrect.
Finally, the menutree on the left tree doesn't work.

Regards,
Edwin
Comment 1 Tommi Tervo 2008-02-20 09:04:32 UTC 
page renders and works fine with safari UA. Feedback part worked fine too. There is bunch of browser UA specific code on js-code:

// Only run if the browser is supported.
if (SiteRecruit_Globals.isInternetExplorer || SiteRecruit_Globals.isMozilla)

http://i2.msdn.microsoft.com/Platform/cjs/ssmoz-bn1759.2.js
if ( ! document.all ){__loadCompat(window);if(window.navigator.userAgent.indexOf('Safari')>=0){_loadSafariCompat(window);}
else{_loadMozillaCompat(window);}}
Comment 2 Maksim Orlovich 2008-03-10 23:20:53 UTC 
*** Bug 158025 has been marked as a duplicate of this bug. ***
Comment 3 Maksim Orlovich 2008-03-10 23:24:12 UTC 
*** Bug 136704 has been marked as a duplicate of this bug. ***
Comment 4 Tommi Tervo 2009-02-25 17:14:11 UTC 
*** Bug 185505 has been marked as a duplicate of this bug. ***
Comment 5 Maksim Orlovich 2009-02-27 16:42:44 UTC 
*** Bug 185704 has been marked as a duplicate of this bug. ***
Comment 6 Maksim Orlovich 2009-06-02 15:16:30 UTC 
*** Bug 194988 has been marked as a duplicate of this bug. ***
Comment 7 Kai Krakow 2009-06-03 00:10:32 UTC 
Maybe it would be convenient if KHTML identifies itself as being safari compatible as QtWebkit does?
Comment 8 Marcus Better 2009-06-03 10:41:50 UTC 
(In reply to comment #7)
> Maybe it would be convenient if KHTML identifies itself as being safari
> compatible as QtWebkit does?

That would be a disaster since it is nowhere near Safari compatible.
Comment 9 Andreas Marschke 2009-06-21 17:00:58 UTC 
agree to comment #8 and not reproducable in 4.2.91
Comment 10 Nicos Gollan 2009-11-24 11:25:55 UTC 
Still an issue in 4.3.2.
Comment 11 Tommi Tervo 2009-12-12 14:52:44 UTC 
*** Bug 218385 has been marked as a duplicate of this bug. ***
Comment 12 Tommi Tervo 2010-03-24 10:01:44 UTC 
*** Bug 231985 has been marked as a duplicate of this bug. ***
Comment 13 Justin Zobel 2021-03-21 00:25:58 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 10 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 14 Christoph Cullmann 2024-05-06 18:39:57 UTC 
Dear user,

KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6.

Please migrate to use a QWebEngine based HTML component.

We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes.

For security issues, please see:

https://kde.org/info/security/

Sorry that we did not fix this issue during the life-time of KHTML.

Greetings
Christoph Cullmann