>>> On Sunday 02 October 2011 02:06:48 Julius Schwartzenberg wrote: >>>> > So here is a list of known issues: >>>> > - buttons like back, forward do not work >>>> > - progress indication seems broken >>>> > - some webpages load and then display a white screen >>>> >>>> I forgot to add. >>>> It's necessary for the kmozilla binary to see two environment >>>> variables >>>> as well. >>>> First of all, it needs to find its libraries and also it needs to know >>>> the location of the Mozilla environment it should use. Something like >>>> this should work: >>>> export LD_LIBRARY_PATH=/usr/lib/xulrunner-1.9.2.23/ >>>> export MOZILLA_FIVE_HOME=/usr/lib/xulrunner-1.9.2.23/ >>>> konqueror >>>> (and open a site and choose kmozilla as the viewer) >>>> >>>> Maybe a kcontrol panel could be added at some point that allows >>>> choosing >>>> the Mozilla environment to use. >>> >>> What is needed to enable this Mozilla support? >>> It seems it wants gtkmozembed.h which is not provided by any devel >>> package. >>> >> >> We are not yet sure if gtkmozembed has been removed in the latest >> xulrunner versions. Right now this is only for systems with Firefox >> less >> than version 5, and work will be done to see if this can be extended to >> later Firefox versions in the future. >> >> Tim > > A bit more information, as gtkmozembed is apparently quite widely used > still: > http://stackoverflow.com/questions/2653686/how-to-compile-a-program-with-gtkmozembed-h > > Tim And straight from the horse's mouth: http://groups.google.com/group/mozilla.dev.embedding/browse_thread/thread/e583472c8b598cd0/c56a4765a70607e5?lnk=gst&q=gtkmozembed#c56a4765a70607e5 Essentially we would need to take over gtkmozembed (which is not a bad thing at all!) if we want to keep using it. From what I can tell that means we put it in our 3rdparty GIT tree and build a little standalone library against xulrunner. Tim