On 2013-01-24 23:40 (GMT-0600) Timothy Pearson composed:


>>> Mozilla has explicitly stated that it will not support embedding Firefox
>>> sessions in any third party application, and has removed all programming
>>> hooks needed for doing so.

>> So Camino is no more?

Its last release was close to a year ago, but.....

> I don't know, sorry. :-)  When I looked into this many months ago the
> interface to the Firefox core was being deprecated and removed, and I have
> heard no information to the contrary since.

SeaMonkey isn't Firefox, yet it uses the same Necko and Gecko as the latest 
Firefox, and gets released concurrently with each FF version bump. Whether or 
not SM includes Firefox in its UA string is optional. So it seems there must 
be a way if there's enough will.

>> http://fm.no-ip.com/SS/dpi1920x1200x144-gecko-konq3-chromium-konq4.png

> To everyone on this list, how does the KDE4 version of KHTML compare with
> WebKit?  Better or worse compatibility with most websites?  If KHTML is
> pretty much the same as WebKit as far as CPU/RAM usage and website
> compatibility, the easiest solution would be to integrate KHTML as a
> kioslave in very much the same way as the old version of KHTML works now
> in TDE...

Since WebKit was started as a fork of KHTML by Apple, it seems the KDE 
developers must be backporting WebKit changes into KHTML in a cherry picking 
fashion, that is to say, leaving out parts that cause display density to be 
ignored, and whatever forces the 3:4 pt/px ratio. As "works" example, you can 
see in the screenshot that current KHTML includes web font support, and 
nominal rendering difference between Konq 4 and latest FF.
-- 
"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/