I have uploaded a browser to Rapidshare.de ,
that I would propose as an official
K-Meleon 0.9.12 - Release Candidate 3 .
It is basically only a security update to
GRE 1.7.12, keeping the old look, with
only a few additional features. This is still based
on 1.7, while Dorian's KM 1.0 is based on 1.8 GRE.
Gecko 1.7.12 of nov/26th/2005.
This Release Candidate 3 should now be ready to become an official release.

Last changes
# Renamed to 0.9.12 to indicate Gecko 1.7.12 being used.
# Some small bugs fixed.
# Macros for Proxies and Hotkeys for URLs added.
# Active X Support for Windows Media Player now can be toggled
from the browser. Do not use until Microsoft patched the wmf - bug.
# Smaller chrome by Guenter.
# Metasearch improved for Layers only mode.
# Adblocking by userContent.css can be enabled/disabled from the browser.
# Adblocking by Hostperm.1 can be edited or stopped from the browser.
# Bugfix for the so-called giant history bug implemented.
This bugfix unfortunately disables Google Maps and GMail.
To enable these services, disable the bugfix temporarily, by clicking
on Tools-->Privacy-->Permissions-->Google Maps/GMail enable/disable.
Afterwards disable again, to get the bugfix back for the rest of the Internet.

Added Features
# Pop-up bug fixed by inclusion of 2 files from earlier GREs.
# Additional Javascript button
# Translation macro
# Some search engines
# Mime Types Editor
# New Flashblock plugin by kko
# New SetDefault.exe by Alain
# Active X Support can be enabled, but only for Windows Media Player.
# Preconfigured Aggreg8 News Reader (click also on the + signs).
# Adblocking by userContent.css and Hostperm.1

Please try my Release Candidate 3 and report possible problems.
Download at :

http://rapidshare.de/files/10459900/K-Meleon0.9.12-RC3.exe.html
or
http://rapidshare.de/files/10460280/K-Meleon0.9.12-RC3.zip.html

Press the button "FREE" at the bottom of the page (javascript enabled) ,
and extract the file into a fresh folder.

NoScript and Adblock extensions could be added in a later version,
because they are not yet sufficiently tested.
Regards to all
Fred

Fred,

Don't know what the story is with the download site, but you may want to find
an alternative. I got this message when I tried to download your new RC.

<<You have downloaded 25118 KB. Want to download more?
Get your PREMIUM-Account now! Instant access! (Or wait 44 minutes)>>

<wry grin>

N

Are you using a proxy ?
Then someone else on the same proxy may have made downloads before.
Fred

Fred,

Hmmm. I'm in a Wi-Fi cafe, on I guess a LAN-style connection. Not sure what the proxy info is here.

N

@ndebord,

Yes, it's probably a proxy problem.

I have often the same problem at work. You must be patient and try where there is not too much people, or try from other access.

A+

Alain & Fred,

Yes, it must have been a proxy problem here in the WiFi Cafe. I employed a kludge and managed to download RC3. Tks for the help.

N

Good work Fred.

In my opinion this could be perfectly the next official K-Meleon (with an installer it will look better). If the people here thinks it so we can use Brian's new key to make it official once tested.

I'm having problems to play Amazon samples but I don't know if this is a problem of my configuration. I use a "send to Windows Media Player" macro that someone sended me long time ago to play this files. If someone is also having trouble with the Amazon samples or the WMP I'll be glad to post my macro and menu modifications here.

A question now. What is this about the Microsoft bug that needs to be fixed by them before using Windows Media Player? I forgot to read a thread here?

The WMF exploit is what he is talking about, I believe. Microsoft released an update today:
http://www.microsoft.com/technet/security/bulletin/ms06-001.mspx

I am not sure if this is a fix or just a temporary measure. The way I understand it, this is a permanent fix. I could be wrong though.

Brian

It seems very stable. We have to find some way around this Gmail/Google maps problem. Most users are not going to look that far into their menus. They will just presume that Gmail/Google Maps doesn't work with K-Meleon and move on.
I am using this right now and it seems to be release candidate material... meaning that I believe it to be very close to looking official.
Do you think the Tools menu is already too packed or could the Proxies menu also fit in there?
I tend to be very particular about grammar/spelling. It bothers me that there is no space in "Javascriptbutton" in (View > Toolbars). Would you please add it, Fred?
Everything that I've tinkered with so far works flawlessly. This is definitely very high quality work.

Brian

You left out the Mime Types chrome, Fred.

Brian

I have everything set to open in a new layer. I tried using the Hotkeys and it would only open in the current tab. I know that I could manually go in and edit the macro, but is there a way of adding options to open in new, current, or background layer... like the URL bar?

Brian

Security test results:

High Risk Vulnerabilities: 0
Medium Risk Vulnerabilities: 0
Low Risk Vulnerabilities: 0

Lookin' good, Fred!

Brian

@ bst82551
I will add the mimetypes.jar. I don't know, why it was forgotten.
I can certainly correct to "javascript button".
For the Hotkeys I think, that it would be too complicated to
offer several versions, where to open them. This would need
a complete set of new accelerators, for example Alt + 1 up
to Alt + 9. So these combinations would not be available for
other tasks, wanted by the user.
But if preferable, Ctrl + 1 etc could always open
in a new layer. I am not sure, what would be the best choice.
Concerning the GMaps/GMail, there is no other possibility
to avoid the giant history bug, and at the same time
using GMaps/GMail, until the Mozilla people eliminate
the bug in a new Gecko version. Otherwise people are
vulnerable to the bug all the time, while browsing.
I described the way how to use them on the Release Notes
page.
I hope everything else will be ok.
I also think that an installer would be a good thing.
I think that Hao and Dorian have the needed programs
for that.
Regards
Fred

As has been mentioned, Microsoft has fixed now in an
intermediate patch the dangerous wmf - bug.

http://www.microsoft.com/technet/security/bulletin/MS06-001.mspx

or wait for the automatic update.
Active-X-Support for Windows Media Player can be
enabled again, but I would still only use it on
trusted sites, as other bugs can be waiting in the
pipeline. I don't think that there is a danger listening
to the streams of official radio stations or Amazon
without previous warnings that have been made
public.
Fred

If you want my opinion about numbering, using gecko version is utterly pointless. It can only bring confusion to the average user. Kmeleon has its numbering, gecko has its own. Did you see a firefox 1.0.12 ?

For the giant history bug, how kmeleon 0.9 is affected ? AFAIK the problem is only with long title, but kmeleon uses only a basic history engine which is ignoring page title.

@Dorian
Read this thread :

http://kmeleonbrowser.org/forum/read.php?f=3&i=7650&t=7650

IThe browser will at least crash, even if the history may not be
concerned, and buffer overflows may be possible, though not easy
to execute.

The numbering is useful, because we want to update the
1.7.x browsers with every new Gecko, so how should we
call the next version ?
We use now Gecko 1.7.12 --> 0.9.12
the next Gecko is 1.7.13 --> 0.9.13 and so on,
to show the update status of K-Meleon 0.9,
and the number will always be beyond 1.0,
which has Gecko 1.8.x/1.9.x .
The number correlates with Gecko, not with Firefox,
as we use Gecko Files, not files of Firefox.
Fred

@Dorian
I can understand what you're saying about the numbering system, but the way it is looking, this will help us to be able to figure out which engine is in which build. I personally prefer this numbering system over the old.

Brian

@Fred -chrome: du hast mtypes gelöscht und mpass gelassen.
ich kann leider nicht mailen. bin begeistert : (
- ehe noch mehr zeit vergeht - versuch ich es hier.
Es scheint alles zu laufen, menus.cfg usw zum testen sind dabei.
Guck es dir mal an - es ist unter help. Ich versuche grad zu finden, warum die
GRE von plus 8 anderes macht als RC 1 bis 3.

The mail server of my provider seems to be down & i hope Fred finds this post.
I have uploaded a 1.7 test crome.

Your Download-Link: http://rapidshare.de/files/10517234/chrome1.7.zip.html
Your Delete-Link: http://rapidshare.de/files/10517234/chrome1.7.zip?killcode=51079

the items are primarily for Fred to see:

since this is no finished work - and maybe will never get finished/bug free
- others are welcome to comment and use
but strictly no garantees or end user support what so ever.
greetings & weekend to all

You the Pop-up bug was fixed by inclusion of 2 files from earlier GREs. Which two file were added and what versions of GRE were each file? I am curious how adding those two files fixed the pop-up bug.

@Fred
Ah, it's in fact a kmeleon bug

@bst82551
Nobody care about the version of gecko, because nobody know the differences (I mean the average user). The only thing the user want to know is that he's up to date. Putting a high number is like you want to fill a year without update in, which is of course impossible.

@Dorian - if user want high nr. lets make Your version 1.5 and 2.0 respectively
and Fred 1.1.7.12 : ) Can we do anything for k-m 0.9 to prevent this buffer overflow?

I'm also curious about which two files solved the pop up bug.

From the sixth post in this thread:
http://kmeleonbrowser.org/forum/read.php?f=1&i=32989&t=32971

Author: Fred (---.50.202.62.cust.bluewin.ch)
Date: 11-28-05 05:38

You can see in your own version, which uses the other update,
that 73 of 127 files in components are from 1.7.5 .
This must not necessarily be dangerous, but you cannot control,
what else has been changed by the Mozilla people, a work,
that we here cannot do. An update to 1.7.12 should ideally
contain all the files.
Because of the pop-up bug it was necessary this time to
use 2 old files : gkwidget.dll from 1.7.5, and to get the right
click context menu back also gklayout.dll from 1.7.8, which was
the last one that works together with gkwidget.dll. It differs only
slightly in size from the latest .dll version.
To have a history box, it was always necessary to keep
embed_lite.dll from the 1.7.5 version, because it is not in GRE
anymore.
All the other files are updated to GRE 1.7.12, and I think that
is how it should be as a basic principle.

Fred




Brian

Well, I see I should read posts more carefully.

I very strongly prefer to call Fred's build 0.9.12 (based on Mozilla 1.7.12)

Because there will someday be a Mozilla 1.7.48 and it would be nice to simply make a K-Meleon 0.9.48

but if we make a K-Meleon 0.9.5 now, we might have to make a very strange and unweildy number in the future (such as 0.9.71 or 0.9.8.2) and try and remember the relationship to Mozilla 1.7.48

Let us leave it to the firefox users to remember that Firefox 1.0.51 will be based upon Mozilla 1.7.48 (and that Firefox 1.0.99.3 will be based upon Mozilla 1.7.98)

and that's just the 1.7.xx branch!

We already have a Firefox 1.5 based on GRE1.8
and in two weeks it will become a Firefox 1.5.xx build based on GRE1.8.0.1

and IN PARALLEL we have a Firefox 1.6a1 based on GRE1.9a1
which WILL SPLIT within 2006 into Firefox 1.?.xx based on GRE1.8.1.1
and Firefox 1.?+.xx based on GRE1.9.0.1

You can see how confusing this already is (and I haven't yet mentioned the corresponding Seamonkey version numbers)

All right, but what when we will have GRE v1.8?

If we call the new K-Meleon based on 1.7.12 K-Meeleon 0.9.12 how will we call a K-Meleon based on GRE 1.8.1?

we already have GRE1.8
GRE1.8.....Seamonkey-1.0b...Km-SM-1.1a_Tabs*........Firefox1.5.0
GRE1.8.....Seamonkey-1.0b...Km-CCF0.04_Tabs.........Firefox1.5.0
GRE1.8.....Seamonkey-1.0b...Km-SM-1.0b_Layers.......Firefox1.5.0


the number change to GRE1.8.0.1 will come this month or early February
-----------PROPOSED-January-product-compatibilty-barrier--------

@Enaitz Jar
I think we are going to use 1.x for GRE's with 1.8.x. This is just the overall impression I get from posts I've read in the past.

Brian

The first one is K-Meleon 1.0 .
This is a browser in development, not mainly an update to
a new Gecko security update. It can stand there on its own,
while the 0.9.x K-Meleons are rather a reinsurance, just
in case the new browser would get considerable problems.
which is always possible, as we are dependent of the work
of the Mozilla/Seamonkey/Firefox crew.
Fred

Fred,

Completely agree since I found FF 1.5 less than compelling, so went back to FF 1.0.7 instead. FF 1.0.7, Moz Suite 1.7.xxx and K-Meleon 0.9xxx are all based on Gecko 1.7xxx code. Seamonkey 1.0b, FF 1.5 and K-Meleon 1.0betas are all based on Gecko 1.8xxx code.

The Gecko1.7.xx line is stable and with periodic bug and security fixes pefectly fine. It will be a fine complement to Dorian's new KM 1.0beta, built on Seamonkey 1.0b code. To keep the naming convention of 0.9xx to match Gecko is a good idea I think. And to have both the 0.9xx K-Meleon and the 1.0 Kemeleon out there ia a very good idea, call it reassurance or whatever.

My stable browser is KM 0.9, GRE 1.7.5 updated with Brian's executable to GRE 1.7.12. I experiment with the newer releases by Dorian, Fred and Hao, but they are not my everyday browser YET.

N