Timothy Pearson composed on 2014-10-15 14:31 (UTC-0500):

> Konqueror's broken HTML rendering is a known
> problem but I haven't gotten around to seeing what would be required to
> replace KHTML with Webkit.  That process will be lengthy and won't happen
> for R14 in any case.

Keep in mind in planning whether to replace or to provide two options as KDE4
does that KHTML is the only rendering engine that completely preserves
physical units as physical units for screen display, e.g. pt, mm, cm, in,
etc. Geckos can do it only via their proprietary mozmm CSS unit, making it as
useless as the others except on pages specifically styled or restyled to use
that unit. All engines except KHTML converted physical units into logical
units to conform with the spec change from CSS2 to CSS3, losing the ability
to present accurate physical sizes on desktops configured to use an accurate
display density.

Example page using pt and mozmm:
http://fm.no-ip.com/Auth/dpi-screen-window.html

Only those who do have physical screen density more than nominally different
from 96 DPI and have X configured to match should see a difference between
e.g. Chrome and Firefox or Konq configured to use KHTML. As X has forced DPI
to 96 for several years, the number of people able to notice is rather small.
IOW, e.g. on a 17" 1920x1200 laptop, where physical density is 133 DPI, if X
is accurately configured to match 133 DPI, the difference among browsers in
font sizes in both page and UI is very striking. Only in Konq & FF will the 1
inch block measure an inch with a physical ruler, and only in Konq & FF will
12pt text measure 12pt physically.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/