Summary: | MSDN pages rendered incorrect | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Edwin Schepers <yez> |
Component: | khtml | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | arvidjaar, crissi99, gtdev, kai, marcus, thunderbird2k, tim.eberhardt, xxtjaxx |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Edwin Schepers
2008-01-08 21:26:04 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);}} *** Bug 158025 has been marked as a duplicate of this bug. *** *** Bug 136704 has been marked as a duplicate of this bug. *** *** Bug 185505 has been marked as a duplicate of this bug. *** *** Bug 185704 has been marked as a duplicate of this bug. *** *** Bug 194988 has been marked as a duplicate of this bug. *** Maybe it would be convenient if KHTML identifies itself as being safari compatible as QtWebkit does? (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. agree to comment #8 and not reproducable in 4.2.91 Still an issue in 4.3.2. *** Bug 218385 has been marked as a duplicate of this bug. *** *** Bug 231985 has been marked as a duplicate of this bug. *** 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. 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 |