Bug 269488

Summary: using KHTMLPart may introduce unnecessary bloat
Product: [Applications] konqueror Reporter: Christopher Yeleighton <giecrilj>
Component: khtmlAssignee: Konqueror Bugs <konqueror-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: wishlist    
Priority: NOR    
Version First Reported In: 4.6.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Christopher Yeleighton 2011-03-26 20:55:12 UTC 
Version:           4.6.0 (using KDE 4.6.0) 
OS:                Linux

The introduction to KHTMLPart suggests that Qt rich text can be used instead.  However, this suggestion applies only to displaying static HTML on screen, which should be explicitly explained, otherwise the information is misleading.  In particular, it should be noted that Qt cannot be used to manipulate (transform) HTML because Qt uses only six basic elements internally: SPAN, BLOCK, LIST, TABLE, ANCHOR and TITLE.  Not even headings are supported.

Reproducible: Always

Steps to Reproduce:
  1. Read the introduction to KHTML API [1].

Actual Results:  
  1. 
  Note that using KHTMLPart may introduce security vulnerabilities 
  and unnecessary bloat to your application. 
  Qt's text widgets are rich-text capable, 
  and will interpret a limited subset of HTML.

Expected Results:  
  Note that using KHTMLPart may introduce security vulnerabilities 
  and unnecessary bloat to your application. 
  If you only need to render static HTML to a graphic display, 
  Qt’s text widgets can convert a limited subset of HTML into rich text.

OS: Linux (x86_64) release 2.6.37.1-1.2-desktop
Compiler: gcc
Comment 1 Christopher Yeleighton 2011-03-26 21:02:40 UTC 
[1] <URL: http://api.kde.org/4.x-api/kdelibs-apidocs/khtml/html/index.html >
Comment 2 Christoph Cullmann 2024-05-06 18:39:01 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