I have problems with favicons transparency that is showed as black color in backgrounds and with scroll bars not showed (similar problem to Fred's SM versions).
I think this happend to mix the new SM chrome.dll (Gecko 1.9) with K-Meleon old chrome (some file lost in chrome). Not worked when I used old K-Meleon chrome.dll.
His speed is impressive!
About K-Meleon web page have some problems to render good.
And browsing I obtain a lot of errors, warnings and messages in Error Console.
Quote desga2
(similar problem to Fred's SM versions).
I think this happend to mix the new SM chrome.dll (Gecko 1.9) with K-Meleon old chrome (some file lost in chrome).
About K-Meleon web page have some problems to render good.
And browsing I obtain a lot of errors, warnings and messages in Error Console.
1.) K-Meleon needs a new chrome. We also made a new chrome when Dorian moved K-Meleon to 1.8. The 1.9 chromes know new defaults and values.
2.) about: draws about.png from a new default location, some other locations have changed also. That is fixed and tested by disrupted, Fred and me.
3.) Error console still needs fixes. I do not know whether I can fix.
The SourceViewer is broken & I have no idea how to fix.
That viewSource.xul of toolkit is no good since it does not guide to the line and place. It only opens the source file. Probable reason no findbar.
Does any one know a method to redirect these blue links in Error console into K-Meleon's own native programmed SourceViewer?
mtypes is broken. I made version 0.3 from Mozilla 1.7.12 code but I can not fix it anymore. This does not matter. A similar tool is in kko's prefs.
Part of the kko's prefs panel seems to want functions that do not exist in 1.9 chrome. He is informed.
4.) How much support for the Toolkit API must stay in/from ./chrome/toolkit.jar?
Edited 4 time(s). Last edit at 02/03/2009 10:50PM by guenter.
I'm like said that his speed (with default settings) in startup and rendering web pages is notable in comparation with official 1.5.x versions with default settings.
And here I am on my aging T40 Thinkpad thinking that the speed of KM 1.5.2 is magnificient when compared to KM 1.0.2 (which is faster than FF and IE6.)
<VBG>
N
Edited 1 time(s). Last edit at 03/14/2009 10:48PM by ndebord.
I'm using the VC8 compiler and don't get the K-Meleon 1.5x Release with Gecko 1.8 to build. Where can I download the src of K-meleon 1.6 based on Gecko 1.9 or when will this be available?
I'm using the VC8 compiler and don't get the K-Meleon 1.5x Release with Gecko 1.8 to build. Where can I download the src of K-meleon 1.6 based on Gecko 1.9 or when will this be available?
Src is in the CVS, the same with 1.5x release however you need to define GECKO_VERSION 19 in the header before building.
Quote ra When can we test a complete package, even if it's only alpha or beta?
Some severe bugs have been introduced with the new JS engine.
While Firefox 3.5.1 is a bugfix release it doesn't fix them all.
Therefore I wouldn't be so impatient for an official new alpha/beta release for now.
Quote bksening
In fact, I am very impatient for an official alpha/beta of KM based on Gecko 1.9.1. KM has languished using old Gecko 1.8.1 far too long.
well why don't you contact Dorian, desga2 or guenter privately and tell them your concerns about when an official alpha/beta of a Gecko 1.9.1x based KM will be available? otherwise, go try out Hao Jiang's KMCCF ME 0.096 browser which is based on Gecko 1.9.1. sheesh!
unlike you, bksening, I can wait as long as I want, even I have to wait a year or two for an official Gecko 1.9.1 based Kmeleon browser to be released.
Edited 3 time(s). Last edit at 08/03/2009 08:40AM by 4td8s.
Sorry I kept silent so long and didn't reply to your post.
The reason, I couldn't give away the source of my information nor the nature of the bugs.
Maybe it would have been wiser to keep my mouth shut up.
However, Firefox 3.5.2 released today will fix several security issues.
I shall contact Dorian, desga2 and guenter about the schedule for Gecko 1.9.1x based K-Meleon. I also wonder why KMCCF ME 0.096 hasn't been made into the official Gecko 1.9.1 KM? But that of course is the difference: will there be an official Gecko 1.9.1 KM or not? The KMCCF one specifically says not official, and that is all the difference.
As well, willingness to wait a year or two for an official Gecko 1.9.1 KM is definitely the wrong mindset. Browser improvements, fixes, enhancements are developed regularly and it certainly it not reasonable nor good to be willing to wait a year or two for Gecko 1.9.1 to get to KM.
Unless KM is going to skip Gecko 1.9.1 entirely? Maybe go straight to whatever Gecko will be used in Firefox 3.6/3.7/4.0 in one or two years time? It will probably be the long awaited Gecko 2.0 revamp by then.
Quote bksening
I shall contact Dorian, desga2 and guenter about the schedule for Gecko 1.9.1x based K-Meleon. I also wonder why KMCCF ME 0.096 hasn't been made into the official Gecko 1.9.1 KM? But that of course is the difference: will there be an official Gecko 1.9.1 KM or not? The KMCCF one specifically says not official, and that is all the difference.
As well, willingness to wait a year or two for an official Gecko 1.9.1 KM is definitely the wrong mindset. Browser improvements, fixes, enhancements are developed regularly and it certainly it not reasonable nor good to be willing to wait a year or two for Gecko 1.9.1 to get to KM.
Unless KM is going to skip Gecko 1.9.1 entirely? Maybe go straight to whatever Gecko will be used in Firefox 3.6/3.7/4.0 in one or two years time? It will probably be the long awaited Gecko 2.0 revamp by then.
FF 3.5xxx is a major change in how that browser works. The decision to use SQLITE for cookies, bookmarks, history and passwords has been an interesting one and there are problems that have been reported all over the place. Whether or not the decision to move from Wallet, etc., was a good one and moving from the old Netscape HTML format was a good one is still yet to be made.
But what it means for a macro based browser like K-Meleon is lots of decisions and changes. This is not an easy upgrade and since (To My Mind) KM 1.5.3 has been a successful and bug-free browser, the decison to make the change and the work required to do so successfully, must be made when it is ready to be Gold code and not a day before.
Play with Hao's versions if you must have 1.9.xxx right this minute. KM has been successful for many years by marching to the beat of its own drummer and to paraphrase an advertising jingle: no release is made before its time (just my two cents worth).
Let me reiterate. This a tough release to make work with KM which does not use XUL/XPI. FireFox, imo, has bet the ranch on SQLite and that is a major, major, yes, major change in the Mozilla Gecko browser and all those who make other browsers based upon Gecko and those who do extensions are scrambling to make sense of this sea change. Not an easy task... not even a little bit.
N
Edited 1 time(s). Last edit at 08/06/2009 09:32AM by ndebord.